29 ms·
There is also systemd-timesyncd and Chrony.
by mbq 12y ago
There is also systemd-timesyncd and Chrony.
- TD-Linux 12y agoFedora (or GNOME 3?) uses Chrony by default due to better power management. I assume the same is true for most other distributions.
- vezzy-fnord 12y agosystemd-timesyncd implements SNTP, which is not the same.
- dfc 12y agosystemd-timesyncd is not much of an alternative. It is simply an sntp client, it does not serve time to other hosts nor can it use reference clocks.
- mbq 12y agoSure, but IMO enough many systems use NTP only in a sntp manner to mention it.
- _wmd 12y agoSNTP is only useful as an option of last resort, e.g. you have no embedded RTC, and no storage to track drift. In all other cases a full NTP client is always preferable, since drift and corrections can be applied without causing jumps to the system clock (triggering software bugs and misfired events), and drift statistics can be recorded -- which is inevitably required in almost all circumstances where you're using even high end PC motherboards that still rely on a $.15 crystal time reference
- xorcist 12y agoSNTP is close to useless. Your time server could be off and you'd happily follow along.