From: Zbigniew Jędrzejewski-Szmek Date: Fri, 15 Sep 2017 07:33:17 +0000 (+0200) Subject: man: delete note about propagating signal termination X-Git-Tag: v235~92^2~6 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=6e2f5000c7a83e3cce336d07395463491fc5f16d;p=platform%2Fupstream%2Fsystemd.git man: delete note about propagating signal termination 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. --- diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 0b8963b..5b82d77 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -753,16 +753,6 @@ considered clean service terminations. - Note that if a process has a signal handler installed - and exits by calling - _exit2 - 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 - Proper - handling of SIGINT/SIGQUIT — How to be a proper - program. - 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