search for: 120sec

W dniu 24.08.2018 o 13:10, Charles Lepple pisze: > Sorry, I didn't mean to imply that the master branch was necessarily going to be different, just wanted to make sure you had everything set up to recompile. The real test is to see if things change after commenting out that line (such as by changing it to start with "//"): > > // { "shutdown.return", 0, 0,

...d shutdown.stayoff instant command to shut down after user-defined delay, just like shutdown.return. Small problem is with delay time: XCP defines this delay time in minutes not in seconds like for "return". The driver converts "shutdowndelay" option to minutes, everything below 120sec means 1 minute. > 2) I added load.on, load.off instant commands. They works as expected > 3) I added test.panel.start command. In XCP this is SYS_TEST but it test front panel on my ups as well > 4) I added shutdowntype config option. The idea is taken from apcsmart.c, 0 (default) means shu...

...id.c line 431  { "shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeReboot", NULL, "1", HU_TYPE_CMD, NUL Change to  { "shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeShutdown", NULL, "120", HU_TYPE_CMD, NULL }, Now, UPS shutdown after 120sec from FSD command, and start from hibernation automaticaly when power is back. Excelent! (I tested 120,180,300 all work) I'm try to set DEFAULT_OFFDELAY and define in ups.conf time to poweroff (offdelay and ondelay), but this is not work. UPS set to poweroff after ~20sec I think this line set...

Hi, I was using kernel-2.6.18-164.15.1 with no known issues. Then, I updated to: Linux 2.6.18-194.17.1.el5 #1 SMP Wed Sep 29 12:50:31 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux I'm aware that there are later updates that patch couple more security bugs. Here is an issue I run with 2.6.18-194.17.1 and am asking if anyone hits that kernel bug. Here are the symptoms: 1) kswapd1 running at 100%,

On Thu, 17 Feb 2005 15:04:50 +0100 Stefan Gofferje <stefan@gofferje.homelinux.org> wrote: > Hi folks, > > I'm registered with sipgate, a German SIP provider. >Configs works fine so far. Trouble is, after a while, it >seems, my registration is dropped by sipgate. How do I >tell * the interval for * registering with a provider? I >suppose, the re-registration

...G ups.test.result: No test initiated ups.timer.reboot: 0 ups.timer.shutdown: -1 ups.vendorid: 051d I have issued upsrw -s battery.charge.low=30 apc1400 and set SHUTDOWNCMD "/bin/systemctl suspend" to reflect the above, so when battery.charge reaches 30% or available battery runtime is 120sec the computer should suspend, which it has done multiple times. I am trying to understand what controls/triggers the UPS reboot signal. 1. Have had the UPS reboot while on power and 100% battery when manually restarting M1 for updates taking down both M1 (during boot, so the signal was delayed?)...