search for: onbatt1

...OTIFYFLAG COMMOK SYSLOG+EXEC NOTIFYFLAG COMMBAD SYSLOG+EXEC NOTIFYFLAG SHUTDOWN SYSLOG+EXEC NOTIFYFLAG REPLBATT SYSLOG+EXEC NOTIFYFLAG NOCOMM SYSLOG+EXEC /etc/nut/upssched.conf LOCKFN /var/lib/nut/upssched.lock PIPEFN /var/lib/nut/upssched.pipe CMDSCRIPT /bin/upssched-cmd AT ONBATT * START-TIMER onbatt1 13 AT ONLINE * CANCEL-TIMER onbatt1 #AT ONBATT * START-TIMER earlyshutdown 30 #AT ONLINE * CANCEL-TIMER earlyshutdown AT ONBATT * START-TIMER onbattwarn 30 AT ONLINE * CANCEL-TIMER onbattwarn when doing: /etc/init.d/ups-monitor restart && tail -f /var/log/syslog output: [ ok ] Restarting...

...not sure if it is a scripting problem or an owner/group problem but when I try to send an email following en event using upssched-cmd, the script exits on the line where I send the email with this message in syslog : Mar 19 20:49:51 chaudron-nautique upssched[1377]: exec_cmd(/path/upssched-cmd onbatt1) returned 78 The log messages prior to the email (logger -t upssched-cmd message) can be found in syslog thus I'm sure that upssched-cmd is called when the event occurs and if I run ~#./upssched-cmd onbatt1as root, the mail is sent properly. I tried a few things regarding privileges on nut...

Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > > both configurations are ok :). Please find the file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here: