Nut upsuser - Sep 2005 - timers and their usage

Hi everyone,

new to the list but a long time nut user.

I've tried a couple of times to set up a timer to avoid getting annoying 
messages when the system goes on battery for only a few seconds.

in uppsched.conf I added this at the bottom:

AT ONBATT * START-TIMER onbattwarn 60
AT ONLINE * CANCEL-TIMER onbattwarn

What am I missing? it still doesn't wait before alerting me.

No, it's set to:

# NOTIFYCMD <command>
NOTIFYCMD /etc/ups/notify.sh


Steven Schoch wrote:
> Did you set NOTIFYCMD in upsmon.conf to upssched?
> 
> In upsmon.conf, the NOTIFYFLAG lines can include SYSLOG, WALL, EXEC.  If 
> you still have WALL set, then upsmon will notify you.  Instead, what you 
> want is for upsmon to call upssched, which does the timer, then calls 
> the program specified as CMDSCRIPT, which has a case line that includes 
> onbattwarn.
> 
> This is a good use for the "else" argument to the "AT"
command.  I
> wanted upssched to notify me, via email to a pager, that the power had 
> been off for over 30 seconds, and then notify me when the power had been 
> restored.  The problem was that if the power was off for less thon 30 
> seconds I still got the "power restored" message.  So I added the
"else"
> argument in upssched.conf so that it runs the "power restored"
command
> only if the timer was no longer running.
> 
That sounds similar to what I'd like to do. Perhaps I could take a peek 
at your config for that scenario?

-Mike

send us back your full upsmon.conf and upssched.conf
there might be some missing directives ...

Arnaud
---
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20050914/70f5eaa2/attachment.html

Arnaud Quette wrote:
> send us back your full upsmon.conf and upssched.conf
> there might be some missing directives ...
> 
Sure

upsmon.conf:

RUN_AS_USER nut
MONITOR quadzilla-ups@localhost 1 nutcase xxx master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
NOTIFYCMD /etc/ups/notify.sh
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
POWERDOWNFLAG /etc/killpower
NOTIFYMSG ONLINE "Quadzilla is on utility power"
NOTIFYMSG ONBATT "Quadzilla is on UPS power"
NOTIFYMSG LOWBATT "Quadzilla UPS in a low battery state"
NOTIFYMSG SHUTDOWN "Quadzilla is being shut down"
NOTIFYMSG FSD "Quadzilla UPS in forced shutdown mode"
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 10


upssched.conf:

CMDSCRIPT /usr/sbin/upssched-cmd
AT ONBATT * START-TIMER onbattwarn 60
AT ONLINE * CANCEL-TIMER onbattwarn