Hi Rick,

Rick Moen writes:

> [...]
>
> The only client to point and laugh at is systemd-timesyncd.

I think it's fair to point out that systemd-timesyncd only promises
Simple NTP (SNTP). How good a job it does of that is another matter
but at least it explains some of the "quirks" you mention below.

> timesyncd does no clock discipline, can't assess the quality of the
> remote time source, doesn't trick jitter and delay over time, and has
> poor accuracy. It also stupidly does disk I/O every single time it
> adjusts the system clock, and doesn't even bother to try adjusting time
> gently, never applying the delta gradually. It's the dumb, crude
> hillbilly of NTP clients; any of the other four is serviceable,
> respectable, capable, and flexible. The systemd team would have been
> much better off incorporating ntimed-client, which is under 5k lines of
> code and implements a full proper NTP client -- competently.
>
> But no. They had to do their own, and do a much worse job at gratuitous
> cost in time and effort.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Software                        https://my.fsf.org/donate
 Join the Free Software Foundation              https://my.fsf.org/join