shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-09 12:58:26 +03:00
Code

man: tone down claims on processes having exited already in ExecStop=

Browse Source 
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:
Lennart Poettering 2024-11-05 13:51:00 +01:00
parent 5adc433799
commit ac804bc2f8
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man/systemd.service.xml
View File

@ -551,11 +551,11 @@
<varname>ExecStop=</varname> – commands specified with this setting are invoked when a service failed to start <varname>ExecStop=</varname> – commands specified with this setting are invoked when a service failed to start
up correctly and is shut down again.</para> 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 <para>It is recommended to use this setting for clean-up operations that shall be executed even when
service failed to start up correctly. Commands configured with this setting need to be able to operate even if the service failed to start up correctly. Commands configured with this setting need to be able to
the service failed starting up half-way and left incompletely initialized data around. As the service's operate even if the service failed starting up half-way and left incompletely initialized data
processes have been terminated already when the commands specified with this setting are executed they should around. As the service's processes have likely exited already when the commands specified with this
not attempt to communicate with them.</para> 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 <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>, service, as well as the main process' exit code and status, set in the <varname>$SERVICE_RESULT</varname>,