I just tried using the upsmon -c fsd while running the development
NUT package. It caused the package to send the 'shutdown' command to
the PC, which caused the PC to shutdown (gracefully), but the UPS
never killed the power to the PC.
Perhaps I misunderstood, but I thought the sequence of
On 09/18/07 11:49, Arjen de Korte wrote:
Mark E. Hansen wrote:
I assume you have read and understood the reasons in the FAQ
why we generally recommend against doing that.
I've read the FAQ and I'm sure I found the entires to which you refer.
However,
what those entries don't consider is
Go for the development version. That has a much improved usbhid-ups
driver, which also allows for better debugging.
I went looking for the Development version, and I'm afraid I'm a little
confused. On the NUT site, it says the latest development version is
2.1, but the release I'm running is
On 09/18/07 06:48, Arjen de Korte wrote:
Alternatively, you might use upsrw and experiment with the value of
'ups.delay.shutdown', which changes the same value in the UPS as the
'load.off' command will. Unfortunately, it doesn't have a
'ups.delay.restart', so you will need to press the power
Mark E. Hansen wrote:
Thanks for the help in getting the current development sources (to Charles
Lepple as well). I've downloaded and configured/installed nut-2.3.0-r1114.
However, I don't see any difference in how the setting of some variables
appears to be ignored.
In that case, chances
Mark E. Hansen wrote:
I assume you have read and understood the reasons in the FAQ
why we generally recommend against doing that.
I've read the FAQ and I'm sure I found the entires to which you refer.
However,
what those entries don't consider is the primary problem with waiting until
the
I'm running Network UPS Tools 2.2.0 on a Linux machine, running
CentOS 4.5 (RedHat Enterprise Linux 4.5), with a kernel version
2.6.9.
I believe I have the software setup and configured properly. I
can access the UPS via the upsc (client) tool, upscmd, upsmon,
etc. Even the CGI pages provide me
Mark Hansen wrote:
I'm running Network UPS Tools 2.2.0 on a Linux machine, running
CentOS 4.5 (RedHat Enterprise Linux 4.5), with a kernel version
2.6.9.
I believe I have the software setup and configured properly. I
can access the UPS via the upsc (client) tool, upscmd, upsmon,
etc. Even
Instant commands supported on UPS [myupsname]:
load.off - Turn off the load immediately
load.on - Turn on the load immediately
shutdown.stop - Stop a shutdown in progress
beeper.on - Enable the UPS beeper
beeper.off - Temporarily mute the UPS beeper
Can anyone please tell me what I'm
On 09/17/07 08:33, Arjen de Korte wrote:
Instant commands supported on UPS [myupsname]:
load.off - Turn off the load immediately
load.on - Turn on the load immediately
shutdown.stop - Stop a shutdown in progress
beeper.on - Enable the UPS beeper
beeper.off - Temporarily mute the UPS beeper
On 09/17/07 10:29, Arjen de Korte wrote:
[...]
Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID: 0x15,
Offset: 0, Size: 16, Value: -60.00
Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID: 0x16,
Offset: 0, Size: 16, Value: -60.00
Here are the culprits.
On 09/17/07 12:45, Arjen de Korte wrote:
Mark E. Hansen wrote:
Apparently, the granualarity on you UPS is 1 minute and it will report the
final time as -60 seconds. This is odd and violates the HID Power Devices
specification. Having said that, it will probably also violate this with
regard
Mark E. Hansen wrote:
Apparently, the granualarity on you UPS is 1 minute and it will report the
final time as -60 seconds. This is odd and violates the HID Power Devices
specification. Having said that, it will probably also violate this with
regard to the fact that a zero delay is a valid
On 09/17/07 12:45, Arjen de Korte wrote:
Go for the development version. That has a much improved usbhid-ups
driver, which also allows for better debugging.
I went looking for the Development version, and I'm afraid I'm a little
confused. On the NUT site, it says the latest development
On 9/17/07, Mark E. Hansen [EMAIL PROTECTED] wrote:
On 09/17/07 12:45, Arjen de Korte wrote:
Go for the development version. That has a much improved usbhid-ups
driver, which also allows for better debugging.
I went looking for the Development version, and I'm afraid I'm a little
15 matches
Mail list logo
