Hi Peter,<br><br><div><span class="gmail_quote">2005/11/8, Peter Selinger <<a href="mailto:selinger@mathstat.dal.ca">selinger@mathstat.dal.ca</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Arnaud Quette wrote:<br>><br>> ...<br>Hi Arnaud,<br><br>I have just tested your CVS commits regarding the socket naming<br>conventions, and I have found that this almost works, but there are<br>some bugs. I am presenting four scenarios (1)-(4) below, of which
<br>three are working correctly but (2) is not.<br>...<br>(2) If I start the driver with:<br>upsdrvctl start mgeusb<br><br>then /var/state/ups shows the following socket and PID file:<br>srw-rw---- 1 root root 0 Nov 7 23:53 newhidups-auto
<br>-rw-r--r-- 1 root root 6 Nov 7 23:53 newhidups-auto.pid<br><br>Upsd *cannot* connect to the driver, and claims the driver is not<br>connected.<br><br>Also, if I try to stop the driver with:<br>upsdrvctl stop mgeusb<br>
<br>then I get this error message:<br><br>Network UPS Tools - UPS driver controller 2.1.0<br>Stopping UPS: mgeusb<br>Can't open /var/state/ups/newhidups-mgeusb.pid: No such file or directory<br><br>Note that this is bizarre, as neither the name of the PID file nor the
<br>name of the socket is the correct one.<br>
</blockquote></div><br>
I've just retested here, and everything's fine.<br>
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<br>
work.<br><br clear="all">If it persists, tell me back and we'll check together.<br>
Arnaud<br>-- <br>Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt<br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://people.debian.org/~aquette/">
http://people.debian.org/~aquette/</a><br>OpenSource Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a>