[Nut-upsuser] Install problems (group permissions) with nut 2.7.2

Manuel Wolfshant wolfy at nobugconsulting.ro
Thu Feb 26 11:55:49 UTC 2015

On 02/26/2015 03:09 AM, Charles Lepple wrote:
> On Feb 25, 2015, at 11:35 AM, Rob Groner <rgroner at RTD.com> wrote:
>> The quickest way to get my UPS running with nut (as the current release exists) is to either:
>> 1)      Add my vendor and device ID to the openups_usb_device_table  OR
>> 2)      Create my own driver file, and then add that driver to the usbhid-ups subdriver_list
>> And then recompile/install.
> Correct.
> For posterity, here's the discussion thread from last March: http://article.gmane.org/gmane.comp.monitoring.nut.devel/6669
> I may not have been clear then, but the changes to the driver/*.c files will definitely require a recompile/install of at least the usbhid-ups driver.
> If you are looking for something more turnkey, you may want to consider building packages for a few of the common distributions. It has been on my TODO list for some time to gather the instructions on how to do this from all of the various mailing list posts, but the information is out there.
     FWIW, I've uploaded rpm packages for nut version 2.6.5 built for 
EL5/x86_64 ( i.e. they should be usable for CentOS 5, Scientific Linux 
5, RHEL 5) at https://wolfy.fedorapeople.org/nut/
     They are backported from the latest version available in Fedora 
EPEL 6 and work fine for me. With enough incentive I might give a spin 
to the latest Fedora packages ( i.e. nut 2.7 ) but at least 2.6.5 is a 
bit newer than the current EPEL 5 packages ( v 2.2.2 ).

     Would you decide to use these packages, please read the official 
docs first as there are incompatibilities, mainly triggered by the 
switch to using tcp_wrappers.
     Please also note that you might need to manually do "usermod -G 
uucp nut" if you upgrade from the current packages as shipped by EPEL 5.


More information about the Nut-upsuser mailing list