[Nut-upsuser] tcp-wrapper not found

Andrew Min Chang laplacezhang at 126.com
Mon Mar 19 03:09:50 UTC 2012







At 2012-03-18 02:26:35,"Charles Lepple" <clepple at 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.

Do you mean that B does not need to run upsd?
Then how does B know which IP to connect with? Does upsmon read upsd.conf, too?
I ran like this, and upsmon printed:
# upsmon
Network UPS Tools upsmon 2.6.3
UPS: MY_UPS at localhost (master) (power value 1)
Using power down flag file /etc/killpower
Just like if there is no any upsd running in my whold workspace.


 >
>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
>
>-- 



Andrew
2012-03-19
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120319/0874343f/attachment.html>


More information about the Nut-upsuser mailing list