From: Marcel Bruinsma on
Am Montag, 12. Oktober 2009 13:17, riggor9999 a écrit :

> pwrstate -pwrfail -delay 60 -active on -cmd
> /etc/pwrstatd-powerfail.sh -duration 1 -shutdown on
>
> The problem is the duration variable ... which can only be
> between 0 and 60 seconds ... which is the length of time you
> must specify the powerfail script (or any other script you
> specify) will take to run before the system shuts down.

As the command (-cmd ...) will run as root, perhaps it
could suspend the daemon by sending it a STOP signal.
When command is finished, it sends a CONT signal to
the daemon. The duration would effectively become
infinite.

--
printf -v email $(echo \ 155 141 162 143 145 154 142 162 165 151 \
156 163 155 141 100 171 141 150 157 157 056 143 157 155|tr \ \\\\)
# Live every life as if it were your last! #
From: Marcel Bruinsma on
Am Montag, 12. Oktober 2009 13:17, riggor9999 a écrit :

> what are other people using if you don't want to / can't use
> the vendor's software.

http://www.networkupstools.org/

The Cyber Power 1500AVR is mentioned in
http://www.networkupstools.org/compat/stable.html

--
printf -v email $(echo \ 155 141 162 143 145 154 142 162 165 151 \
156 163 155 141 100 171 141 150 157 157 056 143 157 155|tr \ \\\\)
# Live every life as if it were your last! #
From: DenverD on
amazing, you bought a UPS unit provides one minute of backup power!
take/send it back.

--
DenverD (Linux Counter 282315) via Thunderbird 2.0.0.23 (20090817),
KDE 3.5.7 "release 72-11", openSUSE Linux 10.3, 2.6.22.19-0.4-default
#1 SMP i686 athlon
From: Günther Schwarz on
riggor9999 wrote:

> So - when I specify duration of 300 using the example above, what
> happens when the power fails is that it takes one minute after the
> power fails for the script to kick off. The script kicks off, and the
> shutdown command waits for 60 seconds max (not the 300 I specified), and
> then proceeds to shutdown ... regardless if the specified script is
> running or completed.

Assuming that the "shutdown command" calls initd with "init 0": why not
letting initd handle your database or whatever you want to terminate
cleanly prior to halting the system? Configured correctly with sufficient
timeouts init will wait for the application to terminate prior to moving
on for the next process.
It is has been mentioned previously that one has to distinguish between
initiating the shutdown and finally cutting power. The latter is an
internal function of the UPS and will depend on the size of the battery.
If the hardware can not provide for sufficient time to do a clean
shutdown it is not suitable for the application. As the battery degrades
in use an undersized UPS will become even more problematic over time.

Günther
From: riggor9999 on
On Oct 12, 9:38 am, DenverD <spam.t...(a)SOMEwhere.dk> wrote:
> amazing, you bought a UPS unit provides one minute of backup power!
> take/send it back.
>
> --
> DenverD (Linux Counter 282315) via Thunderbird 2.0.0.23 (20090817),
> KDE 3.5.7 "release 72-11", openSUSE Linux 10.3, 2.6.22.19-0.4-default
> #1 SMP i686 athlon

you can keep saying it over and over ... but it is still incorrect.
The UPS is 1500VA / 900 watts. My load is 550 watts ... for about 15
to 18 minutes of battery power.

The issue is with the software from the vendor. I have spoken to them
to day and the confirmed the limitation around the runtime of the
scripts prior to shutdown. They will try to update the software.

In the meantime - I can use NUT, or try to add my script to the system
shutdown, return it for another make / model.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: WINE anyone good with it?
Next: Note to HP Printer users