[systemd-devel] clarification on daemon-reload

Igor Bukanov igor at mir2.org
Mon May 18 08:53:15 PDT 2015

On 18 May 2015 at 17:18, Lennart Poettering <lennart at poettering.net> wrote:
> Well, my recommendation is to avoid daemon-reloads during the normal
> boot process if possible, since there are some unresolved issues:

What is then a canonical way to implement initialization when the
configuration comes from a drive that is not available during early
boot like virtio mount or uploaded from a network connection? Clearly
I can write a new persistent config and reboot the system for the new
changes to take an affect, but I would prefer to keep all the config
changes under /run so reboot always brings the system into a clean
state. I.e. how one should implement a staged boot when the system
performs a minimal initialization like mounting some paths or
initializing a minimal networking, gets the rest of the config via
that and then run the rest of initialization?

More information about the systemd-devel mailing list