chrony
 Screenshot of chronyc | |
| Original author(s) | Richard Curnow[1] |
|---|---|
| Developer(s) | Miroslav Lichvar, Red Hat[1] |
| Stable release | 4.5
/ December 5, 2023[2] |
| Repository | |
| Written in | C |
| Operating system | Unix-like |
| Type | Time synchronization |
| License | GNU GPL v2 |
| Website | chrony-project |
chrony is an implementation of the Network Time Protocol (NTP). It is an alternative to ntpd, a reference implementation of NTP. It runs on Unix-like operating systems (including Linux and macOS) and is released under the GNU GPL v2.[3] It is the default NTP client and server in Red Hat Enterprise Linux 8 and SUSE Linux Enterprise Server 15,[4][5] and available in many Linux distributions.[6][7][8]
Support for Network Time Security (NTS) was added in version 4.0.[9]
Comparison with the reference implementation
In contrast to NTPsec, which is a security-focused fork of ntpd, chrony was implemented from scratch.[1] It was designed to synchronize time even in difficult conditions such as intermittent network connections (such as laptops) and congested networks.[1] Some improvements in this regard (compared to reference ntpd) include that it never steps (abruptly adjusts) time outside of startup, can correct for asymmetric network jitters, and can use larger clock rate adjustments on Linux to deal with a broken clock. It typically synchronizes faster and more accurately.[10]
Unlike ntpd, it supports synchronizing the system clock via hardware timestamping (i.e. packet times on the network adapter), improving accuracy of time synchronization between machines on a LAN[3] – to the order of 70 nanoseconds (from asymmetry),[11] comparable to Precision Time Protocol. It also supports synchronization by manual input, so as to perform time correction within an isolated network.[3]
chrony does not implement broadcast, multicast, and anycast modes of operation. It also does not implement the insecure "autokey" authentication.[3] It uses external programs to drive hardware time sources (e.g. gpsd for GNSS), unlike ntpd, which has many built-in drivers.[10]
See also
References
- ^ a b c d Linux Foundation (2017-09-28). "CII Audit Identifies Most Secure NTP Implementation". Linux Foundation. Archived from the original on 2018-02-03. Retrieved 2019-10-08.
- ^ "News". Chrony project. Retrieved 2023-12-14.
- ^ a b c d "Comparison of NTP implementations". Chrony project. Retrieved 2019-10-08.
- ^ "Migrating to chrony". Red Hat, Inc. Archived from the original on 2019-07-16. Retrieved 2019-10-08.
- ^ "Time Synchronization with NTP". SUSE. Retrieved 2019-10-08.
- ^ "chrony". Debian. Retrieved 2019-10-08.
- ^ "chrony". Fedora Packages. Archived from the original on 2019-10-08. Retrieved 2019-10-08.
- ^ "net-misc/chrony". Gentoo Packages. Retrieved 2019-10-08.
- ^ "chrony/chrony.git - Official Git repository for the Chrony project". git.tuxfamily.org. Retrieved 2021-07-31.
- ^ a b "Chapter 18. Configuring NTP Using the chrony Suite Red Hat Enterprise Linux 7". Red Hat Customer Portal.
- ^ "chrony – Configuration examples and accuracy". chrony-project.org.