Am 04.02.2015 um 21:57 schrieb Lennart Poettering:
OK, let's try this again, with an example:
a) you have one service mydaemon.service
b) you have a preparation service called
mydaemon-convert-config.service that takes config from somewhere,
converts it into a suitable format for mydaemon.service's binary
Now, you change that config that is located somewhere, issue a restart
request for m-c-c.s, issue a reload request for mydaemon.service.
Now, something like this should always have the result that your
config change is applied to mydaemon.service. Regardless if
mydaemon.service's start was queued, is already started or is
currently being started. You are suggesting that the reload can
suppressed when a start is already enqueued
which is truethe config change *after* issue restart should not affect the already pending (for whatever reason) restart because this is *unpredictable* bahvior - if i expect that config change to get effective i would issue "systemctl reload" *before* the restart command
if you say that is expected behavior than all the warnings about "you need to enter systemctl deamon-reload because the unit file changed" are pointless and you could just reload automagically all the time
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
