25
25
# normal users can't create the file, due to the possibility of symlinking
28
# NOTE: if you are running Solaris or similar, the permissions that upssched
29
# sets on this file *are not enough* to keep you safe. If your OS ignores
30
# the permissions on a FIFO, then you MUST put this in a protected directory!
32
# Another thing to think about: upsmon doesn't run the NOTIFYCMD as root
33
# unless you run it with -p. So, upssched will probably run as nobody
34
# or similar unless you give upsmon another user with -u. Either way,
35
# you have to set PIPEFN to something that ONLY the resulting upsmon
28
# Note: if you are running Solaris or similar, the permissions that
29
# upssched sets on this file *are not enough* to keep you safe. If
30
# your OS ignores the permissions on a FIFO, then you MUST put this in
31
# a protected directory!
33
# Note 2: by default, upsmon will run upssched as whatever user you have
34
# defined with RUN_AS_USER in upsmon.conf. Make sure that user can
35
# create files and write to files in the path you use for PIPEFN and
38
# My recommendation: create a special directory for upssched, make it
39
# owned by your upsmon user, then use it for both.
38
41
# This is commented out by default to make you visit this file and think
39
42
# about how your system works before potentially opening a hole.
41
# PIPEFN /var/run/upssched.pipe
44
# PIPEFN /var/run/upssched/upssched.pipe
46
# ============================================================================
50
# REQUIRED. This was added after version 1.2.1.
52
# upssched needs to be able to create this filename in order to avoid
53
# a race condition when two events are dispatched from upsmon at nearly
54
# the same time. This file will only exist briefly. It must not be
55
# created by any other process.
57
# You should put this in the same directory as PIPEFN.
59
# LOCKFN /var/run/upssched/upssched.lock
43
61
# ============================================================================
72
90
# -----------------------------------------------------------------------
74
# - CANCEL-TIMER <timername>
92
# - CANCEL-TIMER <timername> [cmd]
76
# Cancel a running timer called <timername>, if possible.
94
# Cancel a running timer called <timername>, if possible. If the timer
95
# has passed then pass the optional argument <cmd> to CMDSCRIPT.
79
98
# If a specific UPS (myups@localhost) comes back online, then stop the
80
99
# timer before it triggers
82
101
# AT COMMOK myups@localhost CANCEL-TIMER upsgone
103
# -----------------------------------------------------------------------
105
# - EXECUTE <command>
107
# Immediately pass <command> as an argument to CMDSCRIPT.
110
# If any UPS (*) reverts to utility power, then execute
111
# 'ups-back-on-line' via CMDSCRIPT.
113
# AT ONLINE * EXECUTE ups-back-on-line
added
removed
conf/upssched.conf
