On Fri, Feb 21, 2014 at 5:13 PM, Tom Gundersen <[email protected]> wrote: > You probably sent this before reading my previous answer, so sorry for > repeating myself: there will soon be cases where (special purpose) > config files are shipped by packages rather than written by > administrators, which is what we want to 'just work'.
Then those other packages and utilities should be responsible for starting systemd-networkd, either with a Requires/After, or via another API for starting it. But keeping it running when there's no use makes little sense. The whole idea of the dependency system is for situations like this one. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
