On Mon, 12 Nov 2018 17:16:10 -0500
Sam Varshavchik wrote:
> At least not until someone goes ahead and implements something that
> preserves existing /dev ownership and permission before shutting down, and
> restoring it at the next boot. That will never happen, of course, for the
> very
Stephen Morris writes:
On 12/11/18 4:10 pm, Sam Varshavchik wrote:
I don't know about ACLs, but how about:
setfacl -m u:nut:rw /dev/bus/usb/006/001
from `man setfacl`
That'll work until the next reboot, when everything gets reset.
Just my two cents worth, from my usage of setfacl
On 12/11/18 4:10 pm, Sam Varshavchik wrote:
Tony Nelson writes:
On 18-11-11 18:43:45, Sam Varshavchik wrote:
I'm trying to get NUT running. It fails to start because it setuids
itself to the nut user and then attempts to open the USB device node,
/dev/bus/usb/006/001
This fails with EACCESS
Sam Varshavchik wrote:
> P.S. This is really an awesome directory to dump configuration files into:
> /usr/lib/udev/rules.d. Apparently, /etc is not good enough, for udev.
/etc is fine for local system config files and udev uses
them. Rules files from packages are placed in /usr/lib.
Having
Tony Nelson writes:
On 18-11-11 18:43:45, Sam Varshavchik wrote:
I'm trying to get NUT running. It fails to start because it setuids
itself to the nut user and then attempts to open the USB device node,
/dev/bus/usb/006/001
This fails with EACCESS because:
[root@monster tmp]# ls -al
On 18-11-11 18:43:45, Sam Varshavchik wrote:
I'm trying to get NUT running. It fails to start because it setuids
itself to the nut user and then attempts to open the USB device node,
/dev/bus/usb/006/001
This fails with EACCESS because:
[root@monster tmp]# ls -al /dev/bus/usb/006/001
I'm trying to get NUT running. It fails to start because it setuids itself
to the nut user and then attempts to open the USB device node, /dev/bus/usb/
006/001
This fails with EACCESS because:
[root@monster tmp]# ls -al /dev/bus/usb/006/001
crw-rw-r--+ 1 root root 189, 640 Nov 11 13:49
