4 ms·
Some might say "fairly complete" is in the eye of the beholder. ;-) Technically OpenNTPD is a "fairly complete implementation" too, but its a waste of time com
by traceroute66 4y ago
Some might say "fairly complete" is in the eye of the beholder. ;-)
Technically OpenNTPD is a "fairly complete implementation" too, but its a waste of time compared to Chrony.
- Beltalowda 4y agoIt's simple, works, synchronizes my clock, and doesn't have a manpage thousands of lines long. It's also explicitly intended not to solve every NTP use case but rather just the common "I want my laptop's clock to be roughly accurate" use case.
- yjftsjthsd-h 4y agoIt refuses to deal with a clock running fast, resulting in my laptop not being accurate. (It usually hovers around 10 minutes in the future)
- Beltalowda 4y agoOh okay, I never had any problems with it, and I've been using it for many years.
- yjftsjthsd-h 4y agoThat's fair; it might be that my hardware clock runs fast and if you don't have that problem it's not a problem.
- mekster 4y agoNot sure why you need a separate NTP client running when systemd has systemd-timesyncd.