Nut upsuser - Feb 2015 - Install problems (group permissions) with nut 2.7.2

Ok, so please correct me if I?m wrong?.

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.

Obviously #1 will be easier at this point, but I understand that it will only
get me the functionality that currently exists in the openups driver (which is
ok, I structured my USB reports around what that driver makes available).  If I
want full functionality I?ll need to eventually make my own driver file.

Sincerely,
Rob Groner

From: Charles Lepple [mailto:clepple at gmail.com]
Sent: Friday, February 20, 2015 7:50 PM
To: Rob Groner
Cc: nut-upsuser List
Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut 2.7.2

On Feb 20, 2015, at 3:15 PM, Rob Groner <rgroner at RTD.com<mailto:rgroner
at RTD.com>> wrote:

Instead, it seems that the usbhid-ups driver will search through its own list of
known devices with vid/pid, and won't "match" my device unless
that device exists as an entry in its device table.  Is that correct?

More or less, yes.

It turns out that UPS vendors all have somewhat different interpretations of the
PDC spec.

There was an idea to create a generic fallback driver that could talk to any USB
HID PDC device:

https://github.com/networkupstools/nut/issues/112

But at the moment, when we suggest passing the 'productid = ' parameter
to usbhid-ups, it is because there is already a set of tables for that vendor,
and their model is not all that different from earlier models.

The nutdrv_qx driver might be more flexible in this regard, since we tend to see
different VID:PID combinations for devices that all speak one of several easily
identifiable dialects of the Megatec Q* protocols.

- Charles Lepple
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150225/21598cbc/attachment.html>

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.

-- 
Charles Lepple
clepple at gmail

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.

         wolfy

Well, having spent a decent amount of time trying to get my driver file added
into the Makefile build system (and failing), I've decided that for now,
simply adding that one line to the openups-hid.c file and recompiling is the
best route to go.  When I can no longer live with the limited nature of the
openups-hid driver, I'll revisit writing our own.

Thanks  for the helps.

Sincerely,
Rob Groner
> -----Original Message-----
> From: Charles Lepple [mailto:clepple at gmail.com]
> Sent: Wednesday, February 25, 2015 8:10 PM
> To: Rob Groner
> Cc: nut-upsuser List
> Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut
> 2.7.2
> 
> 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.
> 
> --
> Charles Lepple
> clepple at gmail
> 
>