[Nut-upsdev] Re: [Nut-upsuser] tripplite_usb interrupt errs

[Arnaud Quette]

2007/1/19, Charles Lepple <clepple at gmail.com>:
> On 1/18/07, Eric A. Hall <ehall at ehsco.com> wrote:
> >
> > On 1/18/2007 9:59 PM, Charles Lepple wrote:
> >
> > > All in all, the tripplite_usb driver for 2.0.5 should be all benefits
> > > and no drawbacks, mostly due to some testing on several different
> > > SMARTPRO 2U models (knock on wood).
> >
> > Can I replace the driver without replacing the whole kit?
> >
> > Compiling is no problem, it's the mess afterwards...
>
> I think there was a change in some of the driver-to-upsd socket
> communication between 2.0.4 and 2.0.5, but it may only affect
> newhidups.
>
> Arnaud, do you remember when that change happened?

Sun Nov 06 20:14:10 UTC 2005 / Arnaud Quette <aquette.dev at gmail.com>

 - the state socket, used for the communication between the drivers
   and upsd, are now named using the upsname, as defined between brackets
   in ups.conf, by default. The same applies to drivers .pid file, now
   named using drivername-upsname. The old naming behavior is kept for
   debug purpose, allowing to start drivers only by specifying a port name.

so post 2.0.4.
This affect all drivers and upsd. So a full update of your installed
tree is required, along with a driver start with "-a upsname"

Arnaud
-- 
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/