[Nut-upsdev] telling apart USB devices

[Arnaud Quette]

Hi Peter,

2005/11/8, Peter Selinger <selinger at mathstat.dal.ca>:
>
> Arnaud Quette wrote:
> >
> > ...
> Hi Arnaud,
>
> I have just tested your CVS commits regarding the socket naming
> conventions, and I have found that this almost works, but there are
> some bugs. I am presenting four scenarios (1)-(4) below, of which
> three are working correctly but (2) is not.
> ...
> (2) If I start the driver with:
> upsdrvctl start mgeusb
>
> then /var/state/ups shows the following socket and PID file:
> srw-rw---- 1 root root 0 Nov 7 23:53 newhidups-auto
> -rw-r--r-- 1 root root 6 Nov 7 23:53 newhidups-auto.pid
>
> Upsd *cannot* connect to the driver, and claims the driver is not
> connected.
>
> Also, if I try to stop the driver with:
> upsdrvctl stop mgeusb
>
> then I get this error message:
>
> Network UPS Tools - UPS driver controller 2.1.0
> Stopping UPS: mgeusb
> Can't open /var/state/ups/newhidups-mgeusb.pid: No such file or directory
>
> Note that this is bizarre, as neither the name of the PID file nor the
> name of the socket is the correct one.
>

I've just retested here, and everything's fine.
I think you have a mixed env. Note that this change affected upsd, upsdrvctl
and drivers. So you have to rebuild / reinstall all for this to
work.

If it persists, tell me back and we'll check together.
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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20051108/11a50021/attachment-0001.html