(please keep the traffic on the list) 2011/6/4 Wayne Thomas <[email protected]>
> Hi Arnaud, > > Hi Wayne > as per http://www.networkupstools.org/docs/man/upsd.users.html, have you >> also set 'actions' and 'instcmds'? >> > > Um, no. I do now!!! > > $ upsrw -s beeper.status=disabled myups > Username (backend): upsuser > Password: > Unexpected response from upsd: ERR READONLY > > I'm not sure what settings should work, but the ones I tried all reported > back as being read-only > calling upsrw with no params will give you the list of supported settings. ie: $ upsrw myups > $ upscmd myups beeper.toggle > Username (backend): upsuser > Password: > OK > the same goes for upscmd with the "-l" option > including the UPS being powered off? >> > > I use upssched with three separate scripts when mains power dies (one > immediate, one after 30 seconds, and one when the UPS is critical). Here is > the syslog when I unplugged the ups and plugged it back in a few seconds > later; is this sufficient? > > Jun 4 14:38:07 backend upsmon[30606]: UPS myups@localhost on battery > Jun 4 14:38:07 backend upssched[1557]: Executing command: power-off > Jun 4 14:38:07 backend upssched-cmd: Uh oh, power is off > Jun 4 14:38:09 backend upssched[1579]: Timer daemon started > Jun 4 14:38:09 backend upssched[1579]: New timer: power-still-off (30 > seconds) > Jun 4 14:38:12 backend upsmon[30606]: UPS myups@localhost on line power > Jun 4 14:38:12 backend upssched[1579]: Cancelling timer: power-still-off > Jun 4 14:38:12 backend upssched[1594]: Executing command: power-on > Jun 4 14:38:12 backend upssched-cmd: Yay, power is back on > Jun 4 14:38:25 backend upssched[1579]: Timer queue empty, exiting > knowing that your UPS support the "low battery" notion is enough. the rest is on the NUT side. cheers, Arno
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
