if you are running Solaris or similar, the permissions that upssched sets on this file are not enough to keep you safe. If your OS ignores the permissions on a FIFO, then you MUST put this in a protected directory!
by default, upsmon(8) will run upssched as whatever user you have defined with RUN_AS_USER in upsmon.conf(8). Make sure that user can create files and write to files in the path you use for PIPEFN and LOCKFN.
My recommendation: create a special directory for upssched, make it owned by your upsmon user, then use it for both.
The stock version of the upssched.conf ships with PIPEFN disabled to make you visit this portion of the documentation and think about how your system works before potentially opening a security hole.
You should put this in the same directory as PIPEFN.
AT notifytype upsname command
This will perform the command command when the notifytype and upsname match the current activity. Possible values for command are:
START-TIMER timername interval
Start a timer that’ll execute when any UPS (*) has been gone for 10 seconds
AT COMMBAD * START-TIMER upsgone 10
CANCEL-TIMER timername [cmd]
If a specific UPS (myups@localhost) comes back online, then stop the timer before it triggers
AT COMMOK myups@localhost CANCEL-TIMER upsgone
If any UPS (*) reverts to utility power, then execute ups-back-on-line via CMDSCRIPT.
AT ONLINE * EXECUTE ups-back-on-line
Note that any AT that matches both the notifytype and the upsname for the current event will be used.
For a complete list of notifytype possible values, refer to the section NOTIFY EVENTS in upsmon(8).
|10/27/2020||Network UPS Tools 2.7.4|