Date: Thu, 10 Jul 2014 06:20:28 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 191777] New: sysutils/nut: messes up permissions in /dev and causes all sorts of problems Message-ID: <bug-191777-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191777 Bug ID: 191777 Summary: sysutils/nut: messes up permissions in /dev and causes all sorts of problems Product: Ports Tree Version: Latest Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: beastie@tardisi.com FreeBSD 9.2-RELEASE-p7 #0: Tue Jun 3 11:05:13 UTC 2014 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC new with nut-2.7+ is /usr/local/etc/devd/nut-usb.conf Which might be useful in principle, but only causes problems. Because it has blocks like this: notify 100 { match "system" "USB"; match "subsystem" "DEVICE"; match "type" "ATTACH"; match "vendor" "0x0001"; match "product" "0x0000"; action "chgrp _ups /dev/$device-name*; chmod g+rw /dev/$device-name*"; }; Where $device-name is undefined, so it reduces to '/dev/*' for the chgrp and chmod operations. The man page says $device-name is one of the variables available for a 'match' block, makes no mention of it being available with 'notify'. Only affects users with USB attached UPSs.. so it stumped me for a while on why it was only happening to this machine. Plus it was secondary, though now it might be the true cause, to the endless cycle of panics from updating to 9.1-RELEASE-p10....instead of the backtraces pointing to vboxnet. Since rolling back to -p9 didn't solve things... -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-191777-13>