[Nut-upsuser] How to tell a battery test is running

Arnaud Quette aquette.dev at gmail.com
Wed May 24 21:54:18 UTC 2006

Hi Scott,

2006/5/24, Scott Tuc Ellentuch at T-B-O-H <ml at t-b-o-h.net>:
> Hi,
>         After I do a :
> upscmd  ellipse at localhost test.battery.start
>         How do I tell its running, what the status is, etc.

I don't have the hardware underhand and it's a long week end here inf
France, but:
- the mge-shut driver has lots of lacks. For example, it expose
commands that might be unsupported by the device (that might be your
case). Moreover, the version in 2.0.3 is really buggy.
If you can, test the subversion Testing branch [1],
- I'm rewritting mge-shut, merging it with newhidups core (both are
really similar, and for the same protocol, excluding bus marshalling).
I'm currently focusing on this rewritte (0,001 % of my time), which
will fixes some bugs and lacks, while completing the data table
(including 3 phase). I've today reached a major step, and I think I'll
be able to commit something next week,
- an "ups.test.result" var. is exposed when supported.

Thanks for your patience,
[1] svn co svn://svn.debian.org/nut/branches/Testing
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

More information about the Nut-upsuser mailing list