[Nut-upsuser] sequence of events / timing upssched/master/slave etc

[Arnaud Quette]

2008/1/29, Charles Lepple <clepple at gmail.com>:
> ...
> There is a pseudo-driver called "dummy-ups" which could be used to
> pass status along to other NUT clients. Your upssched script can then
> call upsrw to modify the ups.status variable on the dummy UPS.

it's interesting that you mention this, since I've worked a bit on
dummy-ups yesterday, fixing some weirdness... And I think for some
time about adding some kind of "meta" mode to allow either to
concatenate data from several units or having some magic formulas to
manage pseudo UPSs.
Example:
[meta]
 driver = dummy-ups
 port = <upsname1>;<upsname2>
 mode = meta

The latter is only the current dummy-ups, with external actions as you
mentioned above (using upsrw...). This is somehow also linked to the
Powersave feature (outlet collection) management that should allow us
to stop only upsmon clients connected on a specific outlet, and which
have a shutdown level (either using a timer or level base).

More thinking needed and comments welcome...
(this thread might move to upsdev)
Arnaud
-- 
Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/