[Nut-upsdev] [nut-commits] svn commit r1043 - in trunk: . docs drivers

[Arnaud Quette]

(still trying triaging my mail stack)

2007/8/11, Arjen de Korte <adkorte-guest at alioth.debian.org>:
> Author: adkorte-guest
> Date: Sat Aug 11 19:31:11 2007
> New Revision: 1043
>
> Log:
> Reworked the 'ups.status' processing of usbhid-ups. Most 'illegally' added status words are now reported as 'ups.alarm'. See the ChangeLog for a more detailed description of what has changed.
> ...
==============================================================================
> --- trunk/ChangeLog     (original)
> +++ trunk/ChangeLog     Sat Aug 11 19:31:11 2007
> @@ -1,3 +1,37 @@
> +   - 'shutdownimm' and 'timelimitexp' no longer map to the LB status
> +     (this was never a good idea, you need OB LB to have an effect).

the ShutdownImminent must be kept as mapped on LB!
it's a complement to BelowRemainingCapacityLimit, and is generally
triggered when OB (linked to ACPresent=0). Other cases are handled by
the hardware through the BYPASS (overload), the RB (replace battery or
internal failure). It has also saved some users life by "launching"
the shutdown sequence. I've even thought about allowing the FSD
setting (or an equivalence) by the driver to force emergency stop.

Since we (MGE) don't use the RemainingTimeLimitExpired nor
FullyDischarged, I can't tell for these ones. But in theory, the
FullyDischarged flag should also trigger LB. If we're OB, then FSD
will come up. Otherwise, there is no real problem...

Arnaud
-- 
Free Software Developer - http://arnaud.quette.free.fr/
Debian Developer - http://people.debian.org/~aquette/
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Ubuntu Media Center (UMC) Project Leader - https://launchpad.net/~umc-team