2010/12/18 Arjen de Korte nut+us...@de-korte.org nut%2bus...@de-korte.org
Citeren David Varley davidavar...@gmail.com:
Given all this, no doubt it is somewhere obvious, when you know where to
look. But I was not planning to be a developer, just a user, and I have a
huge stack of work in
Citeren David Varley davidavar...@gmail.com:
Arjen, now I'm a bit confused. In your script you are saying to shut down
nut before issuing the upsdrvctl command to tell the UPS to start a delayed
shutdown.
Yes.
But as shutting down nut causes the usbhid-ups driver to exit, I
thought that
Arjen de Korte nut+us...@de-korte.org nut%2bus...@de-korte.org wrote:
...
You missed reading the docs/suspend-to-disk.txt file, where it is
explained how you should set this up. If you want to know the details
about this, start reading the remainder of the documents in docs/
before asking.
On Dec 18, 2010, at 7:21 AM, David Varley wrote:
So I downloaded the source to the latest stable release, and I read
everything in the /docs folder. Nothing there, no suspend-to-
disk.txt or any mention of suspend.
It appears that suspend-to-disk did not make it into the 2.4.3 tarball.
Here
Regarding my observation that the processes keep running after I sudo
service nut stop, I found this isn't exactly the case. I think what happens
is that if I forget the sudo in front of the command, it comes up with the
Stopping Nut Tools... Done line, as if it worked, however it actually
failed
Citeren David Varley davidavar...@gmail.com:
As far as setting the shutdown command in a script run when hibernating, I
did this. I created a script, 48nut, in /etc/pm/sleep.d, as follows:
#!/bin/sh
# If we are hibernating due to power-fail, initiate a delayed UPS shutdown
and then stop the
On Fri, 17 Dec 2010 17:41:39 +0100, Arjen de Korte
nut+us...@de-korte.orgnut%2bus...@de-korte.org
wrote:
Citeren David Varley davidavar...@gmail.com:
As far as setting the shutdown command in a script run when hibernating, I
did this. I created a script, 48nut, in /etc/pm/sleep.d, as
Citeren David Varley davidavar...@gmail.com:
I've just set up a CyberPower Value 2200E-GP on a system running Lucid
AMD64, with the current NUT package via apt-get, and it seems to be working
fine for me with the usbhid-ups driver, so I guess it can go in the HCL?
Probably. We'll just need a
Arjen,
I've appended the output of upsc
I'll keep in mind your warning about the upsd server latching the FSD flag
and requiring a restart, however I'm just running the packaged Ubuntu/Lucid
version at this stage so I don't have too much flexibility. NUT seems to be
set up as a service, so that
I've just set up a CyberPower Value 2200E-GP on a system running Lucid
AMD64, with the current NUT package via apt-get, and it seems to be working
fine for me with the usbhid-ups driver, so I guess it can go in the HCL?
I'm using the system to host several virtual servers under KVM, and to make
10 matches
Mail list logo