(As usual, just figured I only replied to Arnaud, not the list ... sigh)
Arnaud Quette wrote:
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
[added back the list as cc]
2007/2/2, Andreas Rust [EMAIL PROTECTED]:
Arnaud Quette wrote:
btw, prefer to use, if possible, the latest nut release (2.0.5 currently)
Would like to, but didn't feel like building an RPM and would like to
stick to it for easier maintenance - especially since
Arnaud Quette schrieb:
[completing a missing sentence...]
be sure to read the mge-shut manpage, for more information and
suitable value settings (ie modifying offdelay also implies to modify
ondelay...)
Arnaud
Thanks a lot - will do!
--
Andreas Rust
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
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.
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
6 matches
Mail list logo
