diff options
| author | Lennart Poettering <lennart@poettering.net> | 2014-05-16 01:33:22 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2014-05-16 01:33:22 +0200 |
| commit | 33169701b0640d3629d4c36cf8c71dc26d2cb7e1 (patch) | |
| tree | cc151ae25c047ab89f9e3d5a36b00f22830d4f91 | |
| parent | 9bdb98c59451ed090f8d35d470a54710f389ce71 (diff) | |
man: clarify that the ExecReload= command should be synchronous
http://lists.freedesktop.org/archives/systemd-devel/2014-May/019054.html
| -rw-r--r-- | man/systemd.service.xml | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index af32ccb878..364ad7d0c8 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -519,6 +519,20 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}</programlisting> following:</para> <programlisting>/bin/kill -HUP $MAINPID</programlisting> + + <para>Note however that reloading a + daemon by sending a signal (as with + the example line above) is usually not + a good choice, because this is an + asynchronous operation and hence not + suitable to order reloads of multiple + services against each other. It is + strongly recommended to set + <varname>ExecReload=</varname> to a + command that no only triggers a + configuration reload of the daemon, + but also synchronously waits for it + complete.</para> </listitem> </varlistentry> |