search for: upsdrvctrl

...the reason I had created ups/nut at the beginning. If adding "-u root" to each command is bad security policy, then I'd like to make sure I use a better method. I've setup NUT several times, and tried following the directions each time, but no matter what I did...I could not get upsdrvctrl to successfully start unless I add "-u root" to it (even if I am root when executing the start command). The directions don't indicate to do that, so I've always figured I have permissions incorrect somewhere. Now I'm finally at the point where I need to get this right. Doe...

...Product}=="005c", MODE="664", GROUP="nut" But so far as I can tell, when I plug in the USB cable from the UPS...it is still not setting it to nut group permissions. I am looking at the file in /dev/usb/hid/hiddev0 (which goes away when I unplug the UPS). Either way, upsdrvctrl still won't start unless I add "-u root". So I think my udev rule is simply not taking somehow. Sincerely, Rob Groner > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Wednesday, February 18, 2015 8:11 PM > To: Rob Groner > Cc...

I am attempting to do a from-scratch install of nut into openSUSE 13.1 so I can document the steps a customer will need to follow to make nut work with our UPS. I'm running into the problem I have always run into, which is permissions. I have created the user "ups" and the group "nut" and made ups a member of that group. I executed: ./configure --with-user=ups

...> crw-rw-r-- 1 root root 189, 128 2007-05-18 01:47 001 > crw-rw-r-- 1 root nut 189, 130 2007-05-22 02:46 003 > > /proc/bus/usb/003: > total 0 > crw-rw-r-- 1 root root 189, 256 2007-05-22 02:44 001 > > also indicates that permissions look OK. > > However, starting with upsdrvctrl still reports driver startup failing > with exit 1. What other things besides permissions errors can cause this? > Normaly it should say something more than 'exit 1'. Did You install from svn ? And if so, did You set the state_path during configure. You may be missing or having th...

..., Rob Groner <rgroner at RTD.com> wrote: > Does this revolve around hotplug and udev? Yes. (Well, technically hotplug was superseded by udev) > In other words, is the idea that the created USB device will be in the "nut" group, Yes. > and thus I'd be able to tell upsdrvctrl to start if I am user "ups"? Or do ups/nut not really play into any of this? The usual startup procedure is to run upsdrvctl as root (such as in a login script). It will automatically drop the driver to ups/nut. However, as you mentioned, that requires udev. I don't have an opens...

...ups/nut at the beginning. If adding "-u > root" to each command is bad security policy, then I'd like to make sure I use > a better method. > > I've setup NUT several times, and tried following the directions each time, > but no matter what I did...I could not get upsdrvctrl to successfully start > unless I add "-u root" to it (even if I am root when executing the start > command). The directions don't indicate to do that, so I've always figured I > have permissions incorrect somewhere. Now I'm finally at the point where I > need to...

Hello Does anybody know if it's possible to monitor a Powercom EBk 500 (RS232)? the trick is that I am using a raspberry pi, it does not have RS232 so I connected a keyspan RS232 to USB adapter, but so far I can?t make this work. Thanks for your time to read this. -Edgar -------------- next part -------------- An HTML attachment was scrubbed... URL:

...is a debug mode for udev that will show what is being parsed when. > But so far as I can tell, when I plug in the USB cable from the UPS...it is still not setting it to nut group permissions. I am looking at the file in /dev/usb/hid/hiddev0 (which goes away when I unplug the UPS). Either way, upsdrvctrl still won't start unless I add "-u root". /dev/bus/usb/*/* is the place to look (the hiddev* nodes are not used by libusb). Once the permissions there look correct, can you post the output of running the driver directly with -D?

On Feb 17, 2015, at 4:37 PM, Rob Groner <rgroner at RTD.com> wrote: > 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. Does the group permissions not get set in these directories upon install? I

On Feb 19, 2015, at 8:43 AM, Rob Groner <rgroner at RTD.com> wrote: > I followed the log messages and found where it had created the udev rule...as Charles said, in /lib/udev/rules.d. It is named 52-nut-xxxx and there is nothing else that starts with 52 in /lib/udev/rules.d or /etc/udev/rules.d. My apologies, I got that backwards in my earlier email. udev applies the rules in numerical

...will show what is being > parsed when. > > > But so far as I can tell, when I plug in the USB cable from the UPS...it is still > not setting it to nut group permissions. I am looking at the file in > /dev/usb/hid/hiddev0 (which goes away when I unplug the UPS). Either > way, upsdrvctrl still won't start unless I add "-u root". > > /dev/bus/usb/*/* is the place to look (the hiddev* nodes are not used by > libusb). Once the permissions there look correct, can you post the output of > running the driver directly with -D?