<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><br><br><div></div><div id="divNeteaseMailCard"></div><br><pre><br>At 2012-03-18 02:26:35,"Charles Lepple" <clepple@gmail.com> wrote:
>On Mar 17, 2012, at 11:46 AM, Andrew Min Chang wrote:
>
>> If I want to make a machine A with a USB UPS physicaly plugged into share its UPS to other machines (for example, B) in the local network, I should run processes like this:
>> 1. A runs driver, and then runs upsd with a config of "LISTEN 127.0.0.1"
>> 2. B runs NO driver, but upsd with a config of "LISTEN <IP of A>"
>>
>> Meanwhile you mentioned that upsd is the network server. Do you mean that upsd on A servers the other upsd on B?
>
>No, A runs the driver, plus upsd with LISTEN <IP of A>. If A needs to shut down based on its own UPS (the usual scenario), then it needs to run upsmon connecting to A's IP or localhost.
>
>B runs upsmon, connecting to A.<br><br>Do you mean that B does not need to run upsd?<br>Then how does B know which IP to connect with? Does upsmon read upsd.conf, too?<br>I ran like this, and upsmon printed:<br><i># upsmon<br>Network UPS Tools upsmon 2.6.3<br>UPS: MY_UPS@localhost (master) (power value 1)<br>Using power down flag file /etc/killpower</i><br>Just like if there is no any upsd running in my whold workspace.<br><br><br> >
>In this case, A is the master, and B is the slave, as described here:
>
>http://www.networkupstools.org/docs/man/upsmon.html#_ups_definitions
>
>--
<br><br><br>Andrew<br>2012-03-19<br> </pre></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>