shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-10-28 03:25:31 +03:00
Code

man: delete note about propagating signal termination

Browse Source 
That advice is generally apropriate for "user" programs, i.e. programs which
are run interactively and used pipelines and such. But it makes less sense for
daemons to propagate the exit signal. For example, if a process receives a SIGTERM,
it is apropriate for it to exit with 0 code. So let's just delete the whole
paragraph, since this page doesn't seem to be the right place for the longer
discussion which would be required to mention all the caveats and considerations.

Fixes #6415.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2017-09-15 09:33:17 +02:00
parent 6d44591141
commit 6e2f5000c7
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man/systemd.service.xml
View File

@ -753,16 +753,6 @@
considered clean service terminations.
</para>
<para>Note that if a process has a signal handler installed
and exits by calling
<citerefentry><refentrytitle>_exit</refentrytitle><manvolnum>2</manvolnum></citerefentry>
in response to a signal, the information about the signal is
lost. Programs should instead perform cleanup and kill
themselves with the same signal instead. See
<ulink url="http://www.cons.org/cracauer/sigint.html">Proper
handling of SIGINT/SIGQUIT — How to be a proper
program</ulink>.</para>
<para>This option may appear more than once, in which case the
list of successful exit statuses is merged. If the empty
string is assigned to this option, the list is reset, all