picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

man: document that ExecStop= needs a synchronous tool

Browse source 
As requested in #199.
This commit is contained in:
Lennart Poettering 2015-06-15 12:05:26 +02:00
parent e8c5393631
commit cceb20c75c
1 changed files with 15 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
man/systemd.service.xml
View file

@ -383,10 +383,21 @@
run, all processes remaining for a service are terminated run, all processes remaining for a service are terminated
according to the <varname>KillMode=</varname> setting (see according to the <varname>KillMode=</varname> setting (see
<citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>). <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
If this option is not specified, the process is terminated If this option is not specified, the process is terminated by
immediately when service stop is requested. Specifier and sending the signal specified in <varname>KillSignal=</varname>
environment variable substitution is supported (including when service stop is requested. Specifier and environment
<varname>$MAINPID</varname>, see above).</para></listitem> 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></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>