X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsd_watchdog_enabled.xml;h=cad92df7af2450cb799058eefd881942ee34feab;hb=eb91eb187b7491e05fb95215b77cb62061f41d08;hp=5b0d7e21cb2b4fc2f303de33f5274b5069e66d51;hpb=494a66821815e8109afa136bd42818b85da38c09;p=elogind.git
diff --git a/man/sd_watchdog_enabled.xml b/man/sd_watchdog_enabled.xml
index 5b0d7e21c..cad92df7a 100644
--- a/man/sd_watchdog_enabled.xml
+++ b/man/sd_watchdog_enabled.xml
@@ -80,7 +80,7 @@
inherited by child processes.
If the usec parameter is
- non-NULL sd_watchdog_enabled()
+ non-NULL, sd_watchdog_enabled()
will return the timeout in µs for the watchdog
logic. The service manager will usually terminate a
service when it did not get a notification message
@@ -94,7 +94,7 @@
WATCHDOG=1.
To enable service supervision with the watchdog
- logic use WatchdogSec= in service
+ logic, use WatchdogSec= in service
files. See
systemd.service5
for details.
@@ -107,7 +107,7 @@
errno-style error code. If the service manager expects
watchdog keep-alive notification messages to be sent,
> 0 is returned, otherwise 0 is returned. Only if
- the return value is > 0 the
+ the return value is > 0, the
usec parameter is valid after
the call.
@@ -129,10 +129,10 @@
variable. The call will ignore these variables if
$WATCHDOG_PID does containe the PID
of the current process, under the assumption that in
- that case the variables were set for a different
+ that case, the variables were set for a different
process further up the process tree.
- For details about the algorithm check the
+ For details about the algorithm, check the
liberally licensed reference implementation sources:
and sd-daemon3.
If the reference implementation is used as