On 19 May 2015 at 12:08, Lennart Poettering <[email protected]> wrote: > On Tue, 19.05.15 08:22, Igor Bukanov ([email protected]) wrote: >> In any case, I thought that if I add >> a dependency like After=my-config-is-ready.target for most default >> services that can be configured, load a config from a mount or >> network, generate unit files and place them under /run and then call >> systemctl daemon-reload, then it would work. But if daemon-reload does >> not affect what was already scheduled, then I need a better plan. > > One option is to add a target you enqueue after installing the new > configuration and reloading. Then, add all units that shall start to > it as dependencies.
Thanks, that is a nice solution that does not sounds like a workaround! And if a custom-network-loaded config wants to disable a services that would be otherwise started by default, it could just mask it. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
