r/frigate: Add udev rules for coral tpu
Since the _frigate.service_ unit depends on _dev-apex_0.device_, `/dev/apex_0` needs to have the `systemd` "tag" on its udev device info. Without this tag, systemd will not "see" the device and thus will not mark the `.device` unit as active.unifi-restore
parent
9b4232d01a
commit
daa602495c
|
@ -0,0 +1,2 @@
|
|||
# vim: set ft=udevrules :
|
||||
SUBSYSTEM=="apex", MODE="0660", GROUP="apex", TAG+="systemd"
|
|
@ -6,3 +6,8 @@
|
|||
service:
|
||||
name: frigate
|
||||
state: restarted
|
||||
|
||||
- name: reload udev
|
||||
command: udevadm control --reload
|
||||
- name: trigger udev
|
||||
command: udevadm trigger
|
||||
|
|
|
@ -98,6 +98,19 @@
|
|||
tags:
|
||||
- config
|
||||
|
||||
- name: ensure udev rules are in place for google coral tpu
|
||||
copy:
|
||||
src: apex.rules
|
||||
dest: /etc/udev/rules.d/65-apex.rules
|
||||
owner: root
|
||||
group: root
|
||||
mode: u=rw,go=r
|
||||
notify:
|
||||
- reload udev
|
||||
- trigger udev
|
||||
tags:
|
||||
- udev
|
||||
|
||||
- name: flush handlers
|
||||
meta: flush_handlers
|
||||
- name: ensure frigate is running
|
||||
|
|
Loading…
Reference in New Issue