chiark
/
gitweb
/
~ianmdlvl
/
elogind.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
9bdb98c
)
man: clarify that the ExecReload= command should be synchronous
author
Lennart Poettering
<lennart@poettering.net>
Thu, 15 May 2014 23:33:22 +0000
(
01:33
+0200)
committer
Lennart Poettering
<lennart@poettering.net>
Thu, 15 May 2014 23:33:22 +0000
(
01:33
+0200)
http://lists.freedesktop.org/archives/systemd-devel/2014-May/019054.html
man/systemd.service.xml
patch
|
blob
|
history
diff --git
a/man/systemd.service.xml
b/man/systemd.service.xml
index af32ccb87816b73810b1ce3c23aef32ecd53d76d..364ad7d0c8a5b8ce1dcb4bd0066f94270ac5cafe 100644
(file)
--- 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>
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>
</listitem>
</varlistentry>