From 99479986ea4f0bb0158da97623f25d6572cf8c09 Mon Sep 17 00:00:00 2001 From: Felipe Sateler Date: Sat, 24 Dec 2016 07:34:26 -0300 Subject: 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 --- man/systemd.service.xml | 14 +++++--------- 1 file 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 $MAINPID, see above). - 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 - SIGKILL 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. + 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 KillMode= and + KillSignal= 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. Note that the commands specified in ExecStop= 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 -- cgit v1.2.3-54-g00ecf