diff options
| author | Felipe Sateler <fsateler@users.noreply.github.com> | 2016-12-24 11:34:26 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2016-12-24 11:34:26 +0100 |
| commit | 99479986ea4f0bb0158da97623f25d6572cf8c09 (patch) | |
| tree | a4e998499350f188c861e0e8813718293174c513 | |
| parent | journalctl: add remote log dir to search path when --merge is passed (#4970) (diff) | |
| download | systemd-99479986ea4f0bb0158da97623f25d6572cf8c09.tar.xz systemd-99479986ea4f0bb0158da97623f25d6572cf8c09.zip | |
man: Align ExecStop= documentation with actual kill behavior (#4974)
The manpage claimed that ExecStop would be followed immediately by
SIGKILL, whereas the actual behavior is to go through KillMode= and
KillSignal= first.
Fixes #4490
| -rw-r--r-- | man/systemd.service.xml | 14 |
1 files changed, 5 insertions, 9 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 684029bdb4..ad91817820 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -390,15 +390,11 @@ variable substitution is supported (including <varname>$MAINPID</varname>, see above).</para> - <para>Note that it is usually not sufficient to specify a - command for this setting that only asks the service to - terminate (for example, by queuing some form of termination - signal for it), but does not wait for it to do so. Since the - remaining processes of the services are killed using - <constant>SIGKILL</constant> immediately after the command - exited, this would not result in a clean stop. The specified - command should hence be a synchronous operation, not an - asynchronous one.</para> + <para>Note that it is usually not sufficient to specify a command for this setting that only asks the service + to terminate (for example, by queuing some form of termination signal for it), but does not wait for it to do + so. Since the remaining processes of the services are killed according to <varname>KillMode=</varname> and + <varname>KillSignal=</varname> as described above immediately after the command exited, this may not result in + a clean stop. The specified command should hence be a synchronous operation, not an asynchronous one.</para> <para>Note that the commands specified in <varname>ExecStop=</varname> are only executed when the service started successfully first. They are not invoked if the service was never started at all, or in case its |