Differences between current version and predecessor to the previous major change of upsmon(8).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Tuesday, June 4, 2002 12:31:22 am | by perry | |
| Older page: | version 2 | Last edited on Tuesday, June 4, 2002 12:31:22 am | by perry | Revert |
@@ -45,9 +45,9 @@
events.
upsmon can monitor multiple systems using a single process.
-Every UPS that is defined in the __
upsmon.conf__
(5)
+Every UPS that is defined in the upsmon.conf(5)
configuration file is assigned a power value and a type
(slave or master).
!!OPTIONS
@@ -71,9 +71,9 @@
stop - stop monitoring and exit
-reload - reread __
upsmon.conf__
(5) configuration
+reload - reread upsmon.conf(5) configuration
file
-d
@@ -116,14 +116,14 @@
this task. If your notification scripts need to run as a
specific user, set it here.
-You can also set this in the __
upsmon.conf__
(5) file with
+You can also set this in the upsmon.conf(5) file with
the RUN_AS_USER directive.
!!UPS DEFINITIONS
-In the __
upsmon.conf__
(5), you must specify at least one
+In the upsmon.conf(5), you must specify at least one
UPS that will be monitored. Use the MONITOR
directive.
@@ -157,9 +157,9 @@
below.
Your ''password'' must match the entry in the
-upsd(8) server's __
upsd.conf__
(5) ACCESS directive
+upsd(8) server's upsd.conf(5) ACCESS directive
for this system.
The ''type'' is either master or slave. In general, a
@@ -233,9 +233,9 @@
The UPS can't be contacted for monitoring.
!!NOTIFY COMMAND
-In __
upsmon.conf__
(5), you can configure a program called
+In upsmon.conf(5), you can configure a program called
the NOTIFYCMD that will handle events that
occur.
@@ -529,9 +529,9 @@
In the event that upsmon can't reach upsd(8), it
declares that UPS
-__
upsmon.conf__
(5). If this
+upsmon.conf(5). If this
happens while that UPS was last known to be on battery, it
is assumed to have gone critical and no longer contributes
to the overall power value.
@@ -543,9 +543,9 @@
upsmon usually gives up root powers for the process that
does most of the work, including handling signals like
SIGHUP to reload the configuration file. This means your
-__
upsmon.conf__
(8) file must be readable by the non-root
+upsmon.conf(8) file must be readable by the non-root
account that upsmon switches to.
If you want reloads to work, upsmon must run as some user
@@ -553,9 +553,9 @@
recommend making a new user just for this purpose, as making
the file readable by
-See the RUN_AS_USER section in __
upsmon.conf__
(8) for
+See the RUN_AS_USER section in upsmon.conf(8) for
more on this topic.
!!SIMULATING POWER FAILURES
@@ -574,9 +574,9 @@
under a desk to find the plug.
!!FILES
-__
upsmon.conf__
(5)
+upsmon.conf(5)
!!SEE ALSO
__Server:__
@@ -588,9 +588,9 @@
__Clients:__
upsc(8), upscmd(8), upsct(8),
-__
upsct2__
(8), upsmon(8)
+upsct2(8), upsmon(8)
__Internet resources:__
