chrony with experimental support for NTS (work in progress - rebases expected)
Fetching latest commit…
Cannot retrieve the latest commit at this time.
This is the README for chrony. What is chrony? =============== chrony is a versatile implementation of the Network Time Protocol (NTP). It can synchronise the system clock with NTP servers, reference clocks (e.g. GPS receiver), and manual input using wristwatch and keyboard. It can also operate as an NTPv4 (RFC 5905) server and peer to provide a time service to other computers in the network. It is designed to perform well in a wide range of conditions, including intermittent network connections, heavily congested networks, changing temperatures (ordinary computer clocks are sensitive to temperature), and systems that do not run continuosly, or run on a virtual machine. Typical accuracy between two machines synchronised over the Internet is within a few milliseconds; on a LAN, accuracy is typically in tens of microseconds. With hardware timestamping, or a hardware reference clock, sub-microsecond accuracy may be possible. Two programs are included in chrony, chronyd is a daemon that can be started at boot time and chronyc is a command-line interface program which can be used to monitor chronyd's performance and to change various operating parameters whilst it is running. What will chrony run on? ======================== The software is known to work on Linux, FreeBSD, NetBSD, macOS and Solaris. Closely related systems may work too. Any other system will likely require a porting exercise. You would need to start from one of the existing system-specific drivers and look into the quirks of certain system calls and the kernel on your target system. How do I set it up? =================== The file INSTALL gives instructions. On supported systems the compilation process should be automatic. You will need a C compiler, e.g. gcc or clang. What documentation is there? ============================ The distribution includes manual pages and a document containing Frequently Asked Questions (FAQ). The documentation is also available on the chrony web pages, accessible through the URL https://chrony.tuxfamily.org/ Where are new versions announced? ================================= There is a low volume mailing list where new versions and other important news relating to chrony is announced. You can join this list by sending mail with the subject "subscribe" to firstname.lastname@example.org These messages will be copied to chrony-users (see below). How can I get support for chrony? and where can I discuss new features, possible bugs etc? ======================================================== There are 3 mailing lists relating to chrony. chrony-announce was mentioned above. chrony-users is a users' discussion list, e.g. for general questions and answers about using chrony. chrony-dev is a more technical list, e.g. for discussing how new features should be implemented, exchange of information between developers etc. To subscribe to either of these lists, send a message with the subject "subscribe" to email@example.com or firstname.lastname@example.org as applicable. When you are reporting a bug, please send us all the information you can. Unfortunately, chrony has proven to be one of those programs where it is very difficult to reproduce bugs in a different environment. So we may have to interact with you quite a lot to obtain enough extra logging and tracing to pin-point the problem in some cases. Please be patient and plan for this! License ======= chrony is distributed under the GNU General Public License version 2. Authors ======= Richard P. Curnow <email@example.com> Miroslav Lichvar <firstname.lastname@example.org> Acknowledgements ================ In writing the chronyd program, extensive use has been made of RFC 1305 and RFC 5905, written by David Mills. The source code of the NTP reference implementation has been used to check the details of the protocol. The following people have provided patches and other major contributions to the program : Lonnie Abelbeck <email@example.com> Benny Lyne Amorsen <firstname.lastname@example.org> Andrew Bishop <email@example.com> Vincent Blut <firstname.lastname@example.org> Stephan I. Boettcher <email@example.com> Goswin Brederlow <firstname.lastname@example.org> Leigh Brown <email@example.com> Erik Bryer <firstname.lastname@example.org> Jonathan Cameron <email@example.com> Bryan Christianson <firstname.lastname@example.org> Juliusz Chroboczek <email@example.com> Christian Ehrhardt <firstname.lastname@example.org> Paul Elliott <email@example.com> Stefan R. Filipek <firstname.lastname@example.org> Mike Fleetwood <email@example.com> Alexander Gretencord <firstname.lastname@example.org> Andrew Griffiths <email@example.com> Walter Haidinger <firstname.lastname@example.org> Juergen Hannken-Illjes <email@example.com> John Hasler <firstname.lastname@example.org> Tjalling Hattink <email@example.com> Liam Hatton <firstname.lastname@example.org> Jachym Holecek <email@example.com> Håkan Johansson <firstname.lastname@example.org> Jim Knoble <email@example.com> Antti Jrvinen <firstname.lastname@example.org> Eric Lammerts <email@example.com> Stefan Lucke <firstname.lastname@example.org> Victor Lum <email@example.com> Kevin Lyda <firstname.lastname@example.org> Paul Menzel <email@example.com> Vladimir Michl <firstname.lastname@example.org> Victor Moroz <email@example.com> Kalle Olavi Niemitalo <firstname.lastname@example.org> Frank Otto <email@example.com> Denny Page <firstname.lastname@example.org> Chris Perl <email@example.com> Gautier PHILIPPON <firstname.lastname@example.org> Andreas Piesk <email@example.com> Andreas Steinmetz <firstname.lastname@example.org> NAKAMURA Takumi <email@example.com> Timo Teras <firstname.lastname@example.org> Bill Unruh <email@example.com> Stephen Wadeley <firstname.lastname@example.org> Bernhard Weiss <email@example.com> Wolfgang Weisselberg <firstname.lastname@example.org> Bernhard M. Wiedemann <email@example.com> Joachim Wiedorn <firstname.lastname@example.org> Ralf Wildenhues <Ralf.Wildenhues@gmx.de> Ulrich Windl <email@example.com> Doug Woodward <firstname.lastname@example.org> Thomas Zajic <email@example.com> Many other people have contributed bug reports and suggestions. We are sorry we cannot identify all of you individually.