On Tue, 03.02.15 14:15, Charles Devereaux ([email protected]) wrote: > My current solution with dhcpcd is a sleep service sending signals to > dhcpcd (give back the lease/reclaim it), something which could be extended > to systemd-networkd, with other signals for other meanings that you may not > want by default, like: > - removing the configuration it did (which is currently kept when > systemd-networkd is stopped, which could be useful in some scenarios to > avoid asking an additional IP address every time) > - starting or stopping the DHCP servers services (which once started keep > running) > > Even if systemd-networkd does not support a fine grained logic as I > regretted in another message about br0, this would at least support most of > the basic scenarios many people will need.
I am pretty sure signals are not a particularly good interface for this. We should add a proper bus API for this one day, but this kinda has to wait until kdbus is a done deal, since networkd runs in early boot, and dbus-daemon is not available in early boot. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
