On Tue, Aug 26, 2014 at 4:21 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Tue, 26.08.14 11:41, Miroslav Lichvar (mlich...@redhat.com) wrote: > >> > > This is useful for installations where some other service than >> > > systemd-timesyncd is used to synchronize the system clock. >> > >> > What's the rationale here? >> >> To have timedated/timedatectl managing the right NTP service on >> distributions like Fedora. > > I don't really think that timedated should manage an NTP server like > ntpd/chrony. timedated's primary job is to be a service to GNOME and > other DEs. But if an admin wants to upgrade to a full NTP server, then > he should really enable/disable that with "systemctl" or a similar > command. >
What's wrong with having standard API for querying whether NTP is enabled on a system? Is it better if every DE has to use home-grown checks multiplied by number of NTP implementations? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
