From: Lennart Poettering Date: Wed, 13 Mar 2019 16:06:05 +0000 (+0100) Subject: man: document that if the main process exits after SIGTERM we go directly to SIGKILL X-Git-Tag: v242-rc1~128^2~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2e34d21b703406f53a72867b11e43631eafea385;p=thirdparty%2Fsystemd.git man: document that if the main process exits after SIGTERM we go directly to SIGKILL Fixes: #8122 --- diff --git a/man/systemd.kill.xml b/man/systemd.kill.xml index 09029c56a32..3a6d076eb19 100644 --- a/man/systemd.kill.xml +++ b/man/systemd.kill.xml @@ -87,22 +87,17 @@ group and the control group continues to exist after stop unless it is empty. - Processes will first be terminated via - SIGTERM (unless the signal to send is - changed via KillSignal=). Optionally, this - is immediately followed by a SIGHUP (if - enabled with SendSIGHUP=). If then, after a - delay (configured via the TimeoutStopSec= - option), processes still remain, the termination request is - repeated with the SIGKILL signal or the - signal specified via FinalKillSignal= (unless - this is disabled via the SendSIGKILL= - option). See - kill2 - for more information. - - Defaults to - . + Processes will first be terminated via SIGTERM (unless the signal to send + is changed via KillSignal=). Optionally, this is immediately followed by a + SIGHUP (if enabled with SendSIGHUP=). If processes still + remain after the main process of a unit has exited or the delay configured via the + TimeoutStopSec= has passed, the termination request is repeated with the + SIGKILL signal or the signal specified via FinalKillSignal= + (unless this is disabled via the SendSIGKILL= option). See + kill2 for more + information. + + Defaults to .