Displaying 9 results from an estimated 9 matches for "run_as_group".
2010 Mar 09
1
Tripp-Lite SU2200XLA problem
...cale_1dot0 },
--- ./scripts/udev/nut-usbups.rules.in.0 2010-03-03 15:59:45.000000000 -0500
+++ ./scripts/udev/nut-usbups.rules.in 2010-03-03 16:00:43.000000000 -0500
@@ -102,6 +102,8 @@
ATTR{idVendor}=="09ae", ATTR{idProduct}=="4002", MODE="664", GROUP="@RUN_AS_GROUP@"
# e.g. TrippLite SmartOnline SU1500RTXL2ua - usbhid-ups
ATTR{idVendor}=="09ae", ATTR{idProduct}=="4003", MODE="664", GROUP="@RUN_AS_GROUP@"
+# e.g. TrippLite SmartOnline SU2200XLA - usbhid-ups
+ATTR{idVendor}=="09ae", ATTR{idProduct}==&...
2007 Oct 30
5
NUT + devd + FreeBSD
...evd
sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\
device-name "ugen[0-9]+";\
match "vendor" "0x\1";\
match "product" "0x\2";\
action "chown @RUN_AS_GROUP@ \/dev\/$device-name*; chmod 660 \/dev\/$device-name*";\
};\
/p' </usr/ports/sysutils/nut/work/nut-2.2.0/scripts/udev/nut-usbups.rules.in | sed -e 's#@RUN_AS_GROUP@#uucp#g' > /usr/local/etc/devd/nut.conf
/etc/rc.d/devd restart
Unfortunately the uucp user is not in operator s...
2007 Mar 04
1
configure: added --with-group
I just committed the --with-group option for configure. One thing is not
quite what I like, but I have no idea how to script this in autoconf.
Currently both RUN_AS_USER and RUN_AS_GROUP have the defaults "nobody"
and "nogroup" respectively. I think this really should be changed to the
following:
- if neither --with-user, nor --with-group are specified, we apply the
defaults "nobody" and "nogroup" (or whatever are sane defaults)
- if both -...
2014 Jul 18
0
NUT + devd + FreeBSD
...SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\
> device-name "ugen[0-9]+";\
> match "vendor" "0x\1";\
> match "product" "0x\2";\
> action "chown @RUN_AS_GROUP@ \/dev\/$device-name*; chmod 660 \/dev\/$device-name*";\
> };\
> /p' </usr/ports/sysutils/nut/work/nut-2.2.0/scripts/udev/nut-usbups.rules.in | sed -e 's#@RUN_AS_GROUP@#uucp#g' > /usr/local/etc/devd/nut.conf
> /etc/rc.d/devd restart
Hi Daniel,
Dusting off this thre...
2011 Jul 27
0
udev regression in 2.6.1 (was: new entry in nut-usbups.rules for orvaldi ups)
...sed
> > publicly in 2.4.2 (Feb. 2010).
> > So it seems you are running an old version.
>
> it was in 2.4.2 udev rules as:
>
> # Belkin F6C1200-UNV - blazer_usb
> ATTR{idVendor}=="0665", ATTR{idProduct}=="5161", MODE="664",
> GROUP="@RUN_AS_GROUP@"
>
> but the 2.6.1 doesn't contain this vendor/product id in udev rules.
>
I was puzzled by your above remark.
so I dug and found a regression in r3012!
I've just fixed it in r3147, and it's scheduled for 2.6.2.
thanks a lot for your report ;-)
cheers,
Arnaud
---------...
2011 Nov 21
3
Confusing Generic USB UPS cannot be matched
I was dropping off junk at the waste transfer station and scarfed a UPS
out of the pile of old TV's and VCR's. It was in good physical condition
and as I expected, the battery was toast. A new RBC-2 battery restored
it to working condition. Then I tried to get it to talk to some
software. And I am having no luck.
The unit is branded as a Nexxtech Model 6118507 650VA imported into
2013 Dec 16
0
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
...t gid 'nut'.
Theoretically, that is the sort of information that we are already gathering from the NUT drivers:
https://github.com/networkupstools/nut/blob/master/tools/nut-usbinfo.pl
That script generates (among other things) the scripts/udev/nut-usbups.rules.in file, which gets its @RUN_AS_GROUP@ token replaced by the group name at configure time. On the Debian 7 (wheezy) box where I just verified that udev works, it is installed to /lib/udev/rules.d/52-nut-usbups.rules
The necessary-and-sufficient set for the udev rules file (once the device is identified as USB) should be ATTR{idVendor}...
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.
2015 Feb 17
4
Install problems (group permissions) with nut 2.7.2
...: ./configure --with-user=ups --with-group=nut --with-usb --with-dev
Looking at the output, I see that it does recognize that I put a user and group into the command line arg.
Doing a grep for the user and group, I see that it is present in many places as "RUN_AS_USER = ups" and "RUN_AS_GROUP = nut"
I then executed a make, and sudo make install.
I had thought that giving the user and the group would mean that the /usr/local/ups/* directories and binaries created by "make install" would have "nut" as their group, but they don't....they have only root:root....