On Oct 2, 2015, at 9:01 PM, Davide Baldini <baldiniebald...@gmail.com> wrote: > > When I manually unplug the mains, the computer waits 3 minutes, shutdowns, > and there it stays. As per the above commands, issued from ups_events.sh, it > is instead supposed to boot up after 6 minutes (360 / 60 seconds) counted > from tâ‚€, the moment of the unplug. After 20 seconds from the shutdown, and > largely before the 6-minutes scheduled cycle, the UPS LEDs indicate the > battery is again fully charged (*). Ever after the shutdown, the UPS appears > to never cycle its output, and the computer doesn't restart.
I'm not sure how this changes things, but the blazer driver ignores any parameters for instant commands (other than "test.battery.start"). It gets the "offdelay" and "ondelay" parameters from the command line or ups.conf. You might consider the "nutdrv_qx" driver instead - it is somewhat more consistent with units for the various timers. I believe you can change the delays at runtime as well, but via upsrw instead of command parameters. Can you explain your test procedure again, with more details as to when you unplug the power, and when the driver attempts to send the shutdown command? You may be running into this: http://www.networkupstools.org/docs/FAQ.html#_i_8217_m_facing_a_power_race -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
