Displaying 2 results from an estimated 2 matches for "udev_event_execute_rul".
Did you mean:
udev_event_execute_rules
2013 Dec 16
0
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
...ly_to_event: GROUP 121 /lib/udev/rules.d/52-nut-usbups.rules:48
[1162876.465627] [17394] udev_rules_apply_to_event: MODE 0664 /lib/udev/rules.d/52-nut-usbups.rules:48
...
[1162876.466653] [17394] udev_rules_apply_to_event: MODE 0664 /lib/udev/rules.d/91-permissions.rules:36
[1162876.466668] [17394] udev_event_execute_rules: no node name set, will use kernel supplied name 'bus/usb/002/004'
[1162876.472267] [17394] udev_node_add: creating device node '/dev/bus/usb/002/004', devnum=189:131, mode=01664, uid=0, gid=121
[1162876.472282] [17394] udev_node_mknod: preserve file '/dev/bus/usb/002/004'...
2013 Dec 15
2
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
On 12/14/2013 09:04 PM, Charles Lepple wrote:
>> Is there someway nut can be modified to probe the 0664 permission usb
>> devices
>>> and then connect as root before dropping permissions back to the "nut"
>>> gid?
> Given that the udev method should still work (and seems to, for handcrafted
> udev rules files), I would like to run that to ground first.