FreeBSD Port: apcupsd-3.10.9

[LarsKöller]

----------

In reply to Gary Bajaj who wrote:
 
> In the event of a power failure, the following processes are started and 
> remain hung.  The CGI does not respond (also hung below).  This has been 
> an issue since 3.10.6.  FreeBSD 4.9.  I have recompiled all ports 
> affected by the gettext upgrade before installing the current apcupsd 
> port.  Thanks.
> 
> >  # ps wax | grep apc
> > 19641  ??  I      0:00.00 /bin/sh /usr/local/etc/apcupsd/apccontrol 
> > mainsback HOSTNAME 1 0
> > 19642  ??  I      0:00.00 /bin/sh /usr/local/etc/apcupsd/mainsback 
> > HOSTNAME 1 0
> > 19644  ??  I      0:00.00 /bin/sh /usr/local/etc/apcupsd/mainsback 
> > HOSTNAME 1 0
> > 19646  ??  S      0:00.00 /usr/local/sbin/apcaccess status
> > 19985  ??  S      0:00.01 /usr/local/www/data/apcupsd/multimon.cgi
> > 89862  ??  Is     0:04.43 /usr/local/sbin/apcupsd --kill-on-powerfail
> 
> 

I notice this, too. There is only a very week contact to the developer 
which means a very delayed response or no response.

I've not the skill nor the time to investigate this further.

Without the configuration samples and the separate option for the 
client maschines it was nearly impossible to use apcupsd in a network 
for more than one machine powered by one UPS.

Sorry and regards

Lars

-- 
E-Mail: Lars.Koeller at Uni-Bielefeld.DE        \  Lars Köller
            lkoeller at FreeBSD.org              \  CC University of
PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \  Bielefeld, Germany 
     Key-ID: A430D499                           \  Tel: +49 521 106 4964
----------- FreeBSD, what else? ---- http://www.freebsd.org -------------