salut Patrick and Andreas,
2007/2/1, Patrick Agrain <[EMAIL PROTECTED]>:
At 15:26 01/02/2007, Andreas Rust wrote:
>Hello,
>
>we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server
>using a serial cable.
>Installed and configured properly are RPM versions of
>
>nut-2.0.3-0.1.fc5
>nut-client-2.0.3-0.1.fc5
>nut-cgi-2.0.3-0.1.fc5
>
>which all work (mostly) fine.
>The server is connected to outlet.0 and properly shuts down when it's
>loosing power after around 20 minutes. It also boots up whenever the ups
>is getting power again.
>
>To outlet.1 there are a few components like a router, a small switch and a
>phone connected.
>
>As to our understanding of , outlet.1.autoswitch.charge.low and
>outlet.1.switchable it should be possible to power off these devices at a
>given battery charge, right?
>
>However, using upsrw or upsset.cgi results in strange behaviour.
>Setting (ups|outlet.x).delay.(shutdown|start) to e.g. 120 returns some
>random value (102, 68, etc.).
Meaby, these parameters decrease as soon as they are programmed. Reading
them back never gives the programmed value.
ups.delay.shutdown and ups.delay.start behaves like this on our MGE UPS.
that's it.
>The value reported by upsc "-1" appears odd to us as well.
Default value ? or re-programmation failed ?
default value.
considering that any *.delay.* value is a timer (at least with mge
units), these are decreased until 0 (action is realised, ie shutdown),
and set back to -1 (not init'ed)
Arnaud
--
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/
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
