On Thu, 21 Aug 2008, Charles Lepple wrote: > The following was from an email thread about a week ago: > > Marius said: > > Everything I did was adding > > perm ugen* 0660 > > own ugen* root:uucp > > perm usb* 0660 > > own usb* root:uucp > > to /etc/devfs.conf > > The default user für nut is uucp on FreeBSD, so no need to add > > another user. Beware of the security implications with these rules! > > What does your devfs.conf look like?
I have this in devfs.rules -> add path 'ugen*' group operator mode 660 And I have a devd file in /usr/local/etc/devd/nut.conf with.. attach 100 { device-name "ugen[0-9]+"; match "vendor" "0x0463"; match "product" "0xffff"; action "chown nutmon: /dev/${device-name}*; chmod 600 /dev/${device-name}*"; }; (I changed the NUT port to run as the nutmon user) And it seems that they conflict - I was ending up with perms like so.. crw-rw---- 1 nutmon operator 0, 100 Aug 7 17:49 /dev/ugen0 crw-rw---- 1 root operator 0, 162 Aug 7 17:49 /dev/ugen0.1 However nutmon should have access to both.. [midget 11:26] ~ >id nutmon uid=95(nutmon) gid=66(uucp) groups=66(uucp),5(operator) I did try temporarily commenting out the ugen entry in devfs.rules so the perms stay at.. crw-rw---- 1 nutmon operator 0, 100 Aug 7 17:49 /dev/ugen0 crw-rw---- 1 nutmon operator 0, 162 Aug 7 17:49 /dev/ugen0.1 but it still fails :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser