[Nut-upsdev] NUT driver update process...

Arnaud Quette aquette.dev at gmail.com
Tue Feb 28 16:03:47 UTC 2012


Hi again Bill,

2012/2/28 William R. Elliot <bill at wreassoc.com>:
> Arnaud' the original reason for this was due to having multiple
> communication channels to the UPS.  It is possible for the non-NUT channel
> to start a UPS delayed shutdown that the NUT master and slaves need to know
> about.  Charles suggested using FSD rather than OB LB to avoid confusing
> messages about a low battery in the log when there isn't a low battery.
> Upsmon still does the work, I think, it is just that the driver is setting
> the flag for upsmon to act on rather than upsmon seeing OB LB and doing the
> same thing.  Can the rules be adjusted?

indeed, rules can (and must) always be adjusted for good reasons.
I've answered to Charles' mail, and proposed a doc amendment.

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/



More information about the Nut-upsdev mailing list