<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2015-08-31 20:32 GMT+02:00 Tomasz Torcz <span dir="ltr"><<a href="mailto:tomek@pipebreaker.pl" target="_blank">tomek@pipebreaker.pl</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">> BTW, is timesyncd == timedated? Because the FESCo ruling was about<br>
> timedated. If it's just a name-change, fine. But if it's a new<br>
> implementation, we may want a new investigation.<br>
<br>
</span> Those are two different things. Timesyncd is simple SNTP client (plus<br>
time restoration over reboot, for things without RTC). Timedated<br>
is providing an API + utility to set system timezone and time and to<br>
toggle external time sync.<br>
There are two implementation of timedated:<br>
– systemd's on, this only toggles timesyncd as synchronisation mechanism<br>
– timedatex, which can toggle arbitrary NTP daemon<br></blockquote><div><br></div></div>Yeah, and the FESCo ticket was answering the question whether it replacing systemd-timedated with timedatex was safe (probably the first instance of two packages fighting over a D-Bus service name) and desirable (for Fedora to keep using a full NTP client, overriding systemd-timedated’s bait-and-switch from supporting the major NTP daemons to only supporting timesyncd).<br></div><div class="gmail_extra"> Mirek<br></div><div class="gmail_extra"><br></div></div>