On Tue, 2014-09-09 at 10:38 +0200, Miroslav Lichvar wrote: > Yeah, that was nice, when it worked as we wanted. Unfortunately, with > the latest systemd the NTP service which is enabled/disabled by > timedated is no longer selected from the services installed on the > systemd, but is now hardcoded to the systemd SNTP client (timesyncd). > > That means the NTP status reported in GNOME settings may be incorrect, > enabling/disabling NTP will do nothing if another NTP service is > enabled > or timesyncd will be enabled even when our default NTP client > (chronyd) is installed. > > https://bugzilla.redhat.com/show_bug.cgi?id=1136905 > > Upstream is not interesting in having this configurable. Should we be > patching timedated? Or GNOME? Miroslav, This is clearly a problem. We don't want the NTP switch in gnome-control-center to stop working just because a distro decided to use an "alternative" NTP client like ntpd or chronyd. It looks like we have three options: (1) carry a downstream patch to systemd, (2) carry a downstream patch to gnome-control-center, or (3) drop chrony from the default install. (Is there any reason to keep chrony?) If all three sets of maintainers are resistant to such a change, then we should escalate to FESCO and let them choose for us. Michael
Attachment:
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
