[systemd-devel] clarification on daemon-reload

Lennart Poettering lennart at poettering.net
Mon May 18 08:14:56 PDT 2015

On Sun, 17.05.15 10:06, Igor Bukanov (igor at mir2.org) wrote:

> Hello,
> suppose a unit B runs just because another unit A contains Requires=B and
> After=B. When B runs, it changes A like adding new dependencies, altering
> Exec command etc and then B calls systemctl daemon-reload. Then the systemd
> uses the new definition for A, right?
> In particular, if according to the new configuration A should not run at
> all because B changed the systemd configuration so A is no longer required
> by any units, then systemd does not run A, right?

No, what is queued is queued. A daemon-reload should leave the execution
queue unmodified, neither remove nor add new entries.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list