[Nut-upsuser] CyberPower Value 2200E-GP

Arjen de Korte nut+users at de-korte.org
Sat Dec 18 19:55:21 UTC 2010

Citeren David Varley <davidavarley op 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 front of me and Xmas coming up, and I would really
> like to get this nailed down and move on, so if you could please point me to
> the required documentation I would be most grateful.

I'm very sorry, but we seem to have an issue with building the  
distribution packages. It has been in the sources since nut-2.4.0, but  
I only just found out that we failed to put it in the source tar ball.  
It's attached to this message. My apologies...

Best regards, Arjen
Please keep list traffic on the list (off-list replies will be rejected)
-------------- next part --------------
Desc: Using suspend to disk
File: suspend-to-disk.txt
Date: 29 December 2008
Auth: Arjen de Korte <adkorte-guest op alioth.debian.org>

Support for suspend to RAM and suspend to disk has been available in
the Linux kernel for a while now. For obvious reasons, suspending to
RAM isn't particularly useful when the UPS battery is getting low,
but suspend to disk may be an interesting concept.

This approach minimizes the amount of disruption which would be caused
by an extended outage.  The UPS goes on battery, then reaches low
battery, and the system takes a snapshot of itself and halts.  Then it
is turned off and waits for the power to return.

Once the power is back, the system reboots, pulls the snapshot back in,
and keeps going from there.  If the user happened to be away when it
happened, they may return and have no idea that their system actually
shut down completely in the middle.

In order for this to work, you need to shutdown NUT (UPS driver, upsd
server and upsmon client) in the suspend script and start them again in
the resume script.  Don't try to keep them running.  The upsd server
will latch the FSD state (so it won't be useable after resuming) and so
will the upsmon client.  Some drivers may work after resuming, but many
don't and some UPS'es will require re-initialization, so it's best not
to keep this running either.

After stopping driver, server and client you'll have to send the UPS
the command to shutdown only if the POWERDOWNFLAG is present.  Note
that most likely you'll have to allow for a grace period after sending 
'upsdrvctl shutdown' since the system will still have to take a
snapshot of itself after that.  Not all drivers support this, so before
going down this road, make sure that the one you're using does.

More information about the Nut-upsuser mailing list