On Fri, 27.03.15 17:01, Colin Walters (walters@xxxxxxxxxx) wrote: > This however would require NetworkManager -> timesyncd > integration. Filed that as > https://bugzilla.gnome.org/show_bug.cgi?id=746911 So, what's missing here is actually a way for NM to tell timesyncd NTP server information... timesyncd gets the data automatically from networkd, but that's a private iface between the two. For us, from the systemd side it really should be timesyncd that pulls the data from networkd, i.e. that the upper layer pulls from the lower layer rather than the lower layer pushing into the upper layer. NM never was never so strict there with the layering... Now, we intend to support NM (or in fact any other external config source) pushing data into timesyncd, but this will probably not happen before kdbus. The reason for this is that timesyncd runs in early boot already, where classic dbus is not available. Adding a bus interface for pushing NTP server info into timesyncd would hence either mean moving timesyncd into late boot or dealing with the complexities of having to reconnect when dbus appears. With kdbus this all goes away, as dbus is then available from earliest boot to latest shutdown. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
