Chrony Reviews and details

Social recommendations and mentions

• NTP Appliance Guidance

  At most I would use servers with a better NTP implementation than classic NTPd. I mostly use Chrony when possible. Then possibly use Google public NTP. Source: 12 months ago

• Firewall ports for ntp and chrony?

  Man pages for both implementations don't tell anything. The chrony.tuxfamily.org FAQs mention that problems can occur behind a firewall, but advice what's required to make it work. Source: over 1 year ago

• Why is it cron and not Chron?

  It's good thing. It's already confusing enough trying to remember which service is cronie and which one is chrony; imagine if the former were chronie instead. Source: over 1 year ago

• Clockwork raises $21M to keep server clocks in sync

  How has Chrony not been mentioned here? https://chrony.tuxfamily.org/. - Source: Hacker News / about 2 years ago

• Linux Server time not updating with NTP

  I spent a few hours trying to work out why ntpd wasn't working on my newish build (when ntp-client etc worked fine) and ended up ditching ntpd and using chrony instead, worked properly immediately out of the box. YMMV... obv... Source: over 2 years ago

• PSA: make sure you have an NTP service active to maximize attestation effectiveness

  Then, install Chrony. Chrony is a modern NTP service that is claimed to be more accurate than timesyncd that comes bundled with e.g. Ubuntu as a part of systemd. Source: over 2 years ago

• Increased frequency of missed attestations - Lighthouse

  Timedatectl claimed my time was in sync and the NTP service was active, yet in reality it was hundreds of milliseconds slow compared to my laptop's time. I'd consider extending timedatectl with chrony; after using it, I haven't had any issues with missed attestations. This was a pretty handy guide. Source: over 2 years ago

• Help making a script to pull time from a webserver

  Maybe it will help to convince you to ntpd (which is a proper solution here, this one you proposed is... Funny ;-)): as rPi can't store time, it was always booting on 1st Jan 1970 for me and many ntpds were claiming the difference is too big for them so they got confused and existed. Only chrony does the job properly. Maybe try it? Source: over 2 years ago