mirror of
https://github.com/systemd/systemd.git
synced 2024-11-23 02:03:37 +08:00
man: tone down claims on processes having exited already in ExecStop=
Processes can easily survive the first kill operation we execute, hence we shouldn't make strong claims about them having exited already. Let's just say "likely" hence. Fixes: #15032
This commit is contained in:
parent
5adc433799
commit
ac804bc2f8
@ -551,11 +551,11 @@
|
||||
<varname>ExecStop=</varname> – commands specified with this setting are invoked when a service failed to start
|
||||
up correctly and is shut down again.</para>
|
||||
|
||||
<para>It is recommended to use this setting for clean-up operations that shall be executed even when the
|
||||
service failed to start up correctly. Commands configured with this setting need to be able to operate even if
|
||||
the service failed starting up half-way and left incompletely initialized data around. As the service's
|
||||
processes have been terminated already when the commands specified with this setting are executed they should
|
||||
not attempt to communicate with them.</para>
|
||||
<para>It is recommended to use this setting for clean-up operations that shall be executed even when
|
||||
the service failed to start up correctly. Commands configured with this setting need to be able to
|
||||
operate even if the service failed starting up half-way and left incompletely initialized data
|
||||
around. As the service's processes have likely exited already when the commands specified with this
|
||||
setting are executed they should not attempt to communicate with them.</para>
|
||||
|
||||
<para>Note that all commands that are configured with this setting are invoked with the result code of the
|
||||
service, as well as the main process' exit code and status, set in the <varname>$SERVICE_RESULT</varname>,
|
||||
|
Loading…
Reference in New Issue
Block a user