db0b0a
diff --git a/watchdog.8 b/watchdog.8
db0b0a
index 9b7c6e7..052b1e1 100644
db0b0a
--- a/watchdog.8
db0b0a
+++ b/watchdog.8
db0b0a
@@ -216,6 +216,7 @@ by
8486e6
 .BR watchdog .
8486e6
 So you can for instance restart the server from your
8486e6
 .IR repair-binary .
8486e6
+See the Systemd section below for additinal information.
8486e6
 .PP
8486e6
 .B watchdog
8486e6
 will try periodically to fork itself to see whether the process
db0b0a
@@ -242,6 +243,8 @@ a given interface for traffic. If no traffic arrives the network is
8486e6
 considered unreachable causing a soft reboot or action from the
8486e6
 repair binary.
8486e6
 .PP
8486e6
+To start the watchdog when network is available see the Systemd section below.
8486e6
+.PP
8486e6
 .B watchdog
8486e6
 can run an external command for user-defined tests. A return code not equal 0
8486e6
 means an error occurred and watchdog should react. If the external command is
db0b0a
@@ -348,6 +351,9 @@ Child process did not return in time.
8486e6
 246
8486e6
 Free for personal watchdog-specific use (was \-10 as an unsigned 8\-bit
8486e6
 number).
8486e6
+.PP
8486e6
+With enforcing SELinux policy please use the /usr/libexec/watchdog/scripts/
8486e6
+for your test-binary configuration.
8486e6
 .TP
8486e6
 245
8486e6
 Reserved for an unknown result, for example a slow background test that is
db0b0a
@@ -375,6 +381,9 @@ repair-maximum
8486e6
 controls the number of successive repair attempts that report 0 (i.e. success) but
8486e6
 fail to clear the tested fault. If this is exceeded then a reboot takes place. If set
8486e6
 to zero then a reboot can always be blocked by the repair program reporting success.
8486e6
+.PP
8486e6
+With enforcing SELinux policy please use the /usr/libexec/watchdog/scripts/
8486e6
+for your repair-binary configuration.
8486e6
 .SH "TEST DIRECTORY"
8486e6
 Executables placed in the test directory are discovered by watchdog on
8486e6
 startup and are automatically executed.  They are bounded time-wise by
db0b0a
@@ -413,6 +422,27 @@ As for the repair binary, the configuration parameter
8486e6
 repair-maximum
8486e6
 also controls the number of successive repair attempts that report success
8486e6
 (return 0) but fail to clear the fault.
8486e6
+.SH SYSTEMD
8486e6
+To start watchdog after the network is available:
8486e6
+.PP
8486e6
+.br
8486e6
+systemctl disable watchdog
8486e6
+.br
8486e6
+systemctl enable NetworkManager-wait-online
8486e6
+.br
8486e6
+systemctl enable watchdog-ping
8486e6
+.PP
8486e6
+
8486e6
+When using custom service pid check with custom service
8486e6
+systemd unit file please be aware the "Requires="
8486e6
+does dependent service deactivation.
8486e6
+Using "Before=watchdog.service" or "Before=watchdog-ping.service"
8486e6
+in the custom service unit file may be the desired operation instead.
8486e6
+See systemd.unit documentation for more details.
8486e6
+
8486e6
+.SH SELINUX
8486e6
+The directories /etc/watchdog.d/ and /usr/libexec/watchdog/scripts/ are
8486e6
+recognized locations for custom executables.
8486e6
 .SH BUGS
8486e6
 None known so far.
8486e6
 .SH AUTHORS
db0b0a
@@ -431,4 +461,4 @@ The watchdog device.
8486e6
 The pid file of the running
8486e6
 .BR watchdog .
8486e6
 .SH "SEE ALSO"
8486e6
-.BR watchdog.conf (5)
8486e6
+.BR watchdog.conf (5), systemd.unit (5)
db0b0a
diff --git a/watchdog.conf.5 b/watchdog.conf.5
db0b0a
index edf7c8b..2803fee 100644
db0b0a
--- a/watchdog.conf.5
db0b0a
+++ b/watchdog.conf.5
db0b0a
@@ -47,7 +47,7 @@ Be careful not to this parameter too low. To set a value less then the
db0b0a
 predefined minimal value of 2, you have to use the \-f command line option.
db0b0a
 .TP
db0b0a
 min-memory = <minpage>
db0b0a
-Set the minimal amount of memory that has to stay free. Note that
db0b0a
+Set the minimal amount of virtual memory that has to stay free. Note that
db0b0a
 this is in memory pages (4kB on x86). Default value is 0 pages which means
db0b0a
 this test is disabled. The page size is taken from the system include files.
db0b0a
 The usable memory is computed from MemFree + Buffers + Cached since buffer
db0b0a
@@ -130,6 +130,7 @@ pidfile = <pidfilename>
db0b0a
 Set pidfile name for daemon test mode.
db0b0a
 This option can be given as often as you like to check several daemons, assuming
db0b0a
 they write their post-forking PID to the specified files.
8486e6
+See the Systemd section in watchdog (8) for more information.
8486e6
 .TP
8486e6
 ping = <ip-addr>
8486e6
 Set IPv4 address for ping mode.
db0b0a
@@ -147,6 +148,8 @@ aliased IP interfaces.
8486e6
 .TP
8486e6
 test-binary = <testbin>
8486e6
 Execute the given binary to do some user defined tests.
8486e6
+With enforcing SELinux policy please use the /usr/libexec/watchdog/scripts/
8486e6
+for your test-binary configuration.
8486e6
 .TP
8486e6
 test-timeout = <timeout in seconds>
8486e6
 User defined tests may only run for <timeout> seconds. Set to 0 for unlimited.
db0b0a
@@ -154,6 +157,8 @@ User defined tests may only run for <timeout> seconds. Set to 0 for unlimited.
8486e6
 repair-binary = <repbin>
8486e6
 Execute the given binary in case of a problem instead of shutting down the
8486e6
 system.
8486e6
+With enforcing SELinux policy please use the /usr/libexec/watchdog/scripts/
8486e6
+for your repair-binary configuration.
8486e6
 .TP
8486e6
 repair-timeout = <timeout in seconds>
8486e6
 repair command may only run for <timeout> seconds. Set to 0 for 'unlimited', but
db0b0a
@@ -188,6 +193,7 @@ Set the schedule priority for realtime mode passed to sched_setscheduler().
8486e6
 .TP
8486e6
 test-directory = <test directory>
8486e6
 Set the directory to run user test/repair scripts.  Default is '/etc/watchdog.d'
8486e6
+The /etc/watchdog.d/ is recognized by SELinux policy.
8486e6
 See the Test Directory section in watchdog(8) for more information.
8486e6
 .TP
8486e6
 log-dir = <log directory>
db0b0a
@@ -202,23 +208,7 @@ large databases or virtual machines might need longer.
db0b0a
 verbose = <level>
db0b0a
 This overrides the command line \-\-verbose option. Generally the verbose mode is
db0b0a
 only enabled for debugging as it creates a lot of syslog chatter, so use this option
db0b0a
-with consideration. Zero is "normal" operation (quiet), while 1 is typically used
db0b0a
-for debugging. Values of 2 or more usually generate far too many messages.
db0b0a
-.TP
db0b0a
-heartbeat-file = <filename>
db0b0a
-For debugging this allows a rolling set of status values to be kept on disk
db0b0a
-.TP
db0b0a
-heartbeat-stamps = <interval>
db0b0a
-For debugging this sets the number of entries in the <heartbeat-file>
db0b0a
-.TP
db0b0a
-log-killed-pids = <yes|no>
db0b0a
-This acts like enabling 'verbose' logging, but only for a system reboot, where it
db0b0a
-enables the logging of the PID values for all processes that are being killed. The
db0b0a
-results are written to the killall5.log file in the log directory (if at all
db0b0a
-possible) in this case.
db0b0a
-Intended for debugging cases where you would like to know what was running at the
db0b0a
-point the machine triggered the watchdog, but don't want syslog filling up with the
db0b0a
-usual chatter of activity.
db0b0a
+with consideration.
db0b0a
 .SH FILES
db0b0a
 .TP
db0b0a
 .I /etc/watchdog.conf