For the record.
The quick fix for Apcupsd 3.10.6 hangup problems was
to delete the "apcaccess status" parts out of the
scripts in /usr/local/etc/apcupsd/. (commok,
onbattery, etc...). Event messages still get "wall"ed
and mail still gets sent. Just non of the UPS status
information in messages. Th
Did forget to mention that I made the port with
--enable-net
--- Dave McCammon <[EMAIL PROTECTED]> wrote:
> Anyone have a master/slave or an NIS setup working
> correctly that can share some insight?
>
> If power is pulled from UPS, the master sends the
> warning to its console but...
>
> -the
My bad
Subject should be apcupsd 3.10.6 master/slave setup
(from ports)
--- Dave McCammon <[EMAIL PROTECTED]> wrote:
> Anyone have a master/slave or an NIS setup working
> correctly that can share some insight?
>
> If power is pulled from UPS, the master sends the
> warning to its console but...
Anyone have a master/slave or an NIS setup working
correctly that can share some insight?
If power is pulled from UPS, the master sends the
warning to its console but...
-the slaves lose their connection to the master
-an "apcaccess status" on the master after plug is
pulled will hang.
-when ups
