From f8bdff40eb3060586a7a385e7879f519b9af7d51 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Mon, 8 Apr 2024 20:51:17 +0200 Subject: Merging upstream version 252.23. Signed-off-by: Daniel Baumann --- man/systemd.service.xml | 79 ++++++++++++++++++------------------------------- 1 file changed, 29 insertions(+), 50 deletions(-) (limited to 'man/systemd.service.xml') diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 40c3173..c5207d9 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -765,62 +765,41 @@ Restart= - Configures whether the service shall be - restarted when the service process exits, is killed, or a - timeout is reached. The service process may be the main - service process, but it may also be one of the processes - specified with ExecStartPre=, - ExecStartPost=, - ExecStop=, - ExecStopPost=, or - ExecReload=. When the death of the process - is a result of systemd operation (e.g. service stop or - restart), the service will not be restarted. Timeouts include - missing the watchdog "keep-alive ping" deadline and a service - start, reload, and stop operation timeouts. - - Takes one of - , - , - , - , - , - , or - . - If set to (the default), the service will - not be restarted. If set to , it - will be restarted only when the service process exits cleanly. + Configures whether the service shall be restarted when the service process exits, + is killed, or a timeout is reached. The service process may be the main service process, but it may + also be one of the processes specified with ExecStartPre=, + ExecStartPost=, ExecStop=, ExecStopPost=, + or ExecReload=. When the death of the process is a result of systemd operation + (e.g. service stop or restart), the service will not be restarted. Timeouts include missing the watchdog + "keep-alive ping" deadline and a service start, reload, and stop operation timeouts. + + Takes one of , , , + , , , or + . If set to (the default), the service will not be restarted. + If set to , it will be restarted only when the service process exits cleanly. In this context, a clean exit means any of the following: exit code of 0; - for types other than - Type=oneshot, one of the signals - SIGHUP, - SIGINT, - SIGTERM, or - SIGPIPE; + for types other than Type=oneshot, one of the signals + SIGHUP, SIGINT, + SIGTERM, or SIGPIPE; + exit statuses and signals specified in SuccessExitStatus=. - If set to - , the service will be restarted - when the process exits with a non-zero exit code, is - terminated by a signal (including on core dump, but excluding - the aforementioned four signals), when an operation (such as - service reload) times out, and when the configured watchdog - timeout is triggered. If set to , - the service will be restarted when the process is terminated - by a signal (including on core dump, excluding the - aforementioned four signals), when an operation times out, or - when the watchdog timeout is triggered. If set to - , the service will be restarted only - if the service process exits due to an uncaught signal not - specified as a clean exit status. If set to - , the service will be restarted - only if the watchdog timeout for the service expires. If set - to , the service will be restarted - regardless of whether it exited cleanly or not, got terminated - abnormally by a signal, or hit a timeout. + If set to , the service will be restarted when the process exits with + a non-zero exit code, is terminated by a signal (including on core dump, but excluding the aforementioned + four signals), when an operation (such as service reload) times out, and when the configured watchdog + timeout is triggered. If set to , the service will be restarted when + the process is terminated by a signal (including on core dump, excluding the aforementioned four signals), + when an operation times out, or when the watchdog timeout is triggered. If set to , + the service will be restarted only if the service process exits due to an uncaught signal not specified + as a clean exit status. If set to , the service will be restarted + only if the watchdog timeout for the service expires. If set to , the service + will be restarted regardless of whether it exited cleanly or not, got terminated abnormally by + a signal, or hit a timeout. Note that Type=oneshot services will never be restarted + on a clean exit status, i.e. and are rejected + for them. Exit causes and the effect of the <varname>Restart=</varname> settings -- cgit v1.2.3