X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=man%2Fsd_notify.xml;h=3046ca88ee728c703d7b411406db05b92c564ecd;hb=4b381a9ef65d68dc79760b093436a9c81f43fa5d;hp=5d6ae657018cf2f70464686728e487ba39720ba3;hpb=30ce657e5dc3ca038f5703a610dc65189cd750ed;p=thirdparty%2Fsystemd.git diff --git a/man/sd_notify.xml b/man/sd_notify.xml index 5d6ae657018..3046ca88ee7 100644 --- a/man/sd_notify.xml +++ b/man/sd_notify.xml @@ -1,10 +1,7 @@ - - + - - + @@ -176,6 +173,18 @@ watchdog is enabled. + + WATCHDOG=trigger + + Tells the service manager that the service detected an internal error that should be handled by + the configured watchdog options. This will trigger the same behaviour as if WatchdogSec= is + enabled and the service did not send WATCHDOG=1 in time. Note that + WatchdogSec= does not need to be enabled for WATCHDOG=trigger to trigger + the watchdog action. See + systemd.service5 for + information about the watchdog behavior. + + WATCHDOG_USEC=… @@ -191,7 +200,7 @@ Tells the service manager to extend the startup, runtime or shutdown service timeout corresponding the current state. The value specified is a time in microseconds during which the service must send a new message. A service timeout will occur if the message isn't received, but only if the runtime of the - current state is beyond the original maximium times of TimeoutStartSec=, RuntimeMaxSec=, + current state is beyond the original maximum times of TimeoutStartSec=, RuntimeMaxSec=, and TimeoutStopSec=. See systemd.service5 for effects on the service timeouts.