Am 26.11.2014 um 21:52 schrieb Tom Gundersen:
This sort of scheme (mounting partitions with extra config files after the daemons have started) is not really something we support. We would rather recommend you mount everything you need for your base system (i.e., all of /etc and /usr, but not necessarily /var, /home, ...) from your initrd so that it is all there once your real userspace is started. That said, it _should_ just work to simply restart the relevant services (i.e., systemd-networkd and wpa_supplicant), or better you, just order them After= the relevant mount units (the latter will only work if you don't need any networking before this point of course). Please note that 'systemctl daemon-reload' only reloads the configuration of PID1 itself, and not of the individual daemons, so that is probably what tripped you up.
Thanks a lot for these tips! Ordering networkd with After= in a .conf file works fine. Best regards, Matthias _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
