2010/12/18 Arjen de Korte
>
> Citeren David Varley :
>
> 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 front of me and Xmas coming up, and I would really
>> like to ge
Citeren David Varley :
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 front of me and Xmas coming up, and I would really
like to get this nailed down and move on, so if you c
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
Arjen de Korte > 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.
>
> Best regards, Arjen
Arjen,
That docume
Citeren David Varley :
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 would prevent the command
On Fri, 17 Dec 2010 17:41:39 +0100, Arjen de Korte
> wrote:
>
>
> Citeren David Varley :
>
> 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-f
Citeren David Varley :
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 nut services
# If we are
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
fa
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
Citeren David Varley :
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 little more information
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
th
11 matches
Mail list logo