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