<br><br><div><span class="gmail_quote">2005/11/6, 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>I believe this will not quite work when starting the driver manually<br>without -a. In this case, there is no way for upsd to know what actual<br>device is connected to the driver, and therefore, there will be no way
<br>for commands like "upsc upsname@host" to work. On the other hand, I<br>see no way around this problem. It means, if one wants to use upsd,<br>one always has to start the driver with "-a" (even for non-USB
<br>devices). It this okay? Or do you want to change the behavior only for<br>newhidups, and retain the old behavior for all other drivers?</blockquote><div><br>
yep, I should have given more details.<br>
This behavior (starting the driver without -a and upsd being able to
server its data) which we'll call "unnamed ups", goes back to a time
when we were able to call "upsc localhost".<br>
<br>
Now, users are using the conf files, and upsdrvctl or drv -a. So the
only need to start the drv manually (without -a) is only for debug
purpose.<br>
Thus we don't have to care about upsd communication, and the socket filename can be a dummy value. We only create it for compat...<br>
</div><br>
So this new behavior becomes the standard.<br>
<br>
Arnaud<br>
</div>