The Network Time Protocol (NTP) daemon provided by the ntp package is by far the easiest way to manage the accuracy of your clock, particularly if you are connected to the internet (even if only intermittently).
The ntp daemon (ntpd) effectively sets the clock by speeding it up or slowing it down depending on its natural drift so that it gets in sync and stays there. This avoids a ``sudden shock’’ to the system with a dramatic change to the time, although mostly the system can handle it.
The primary configuration required is to identify an NTP server. Look at the lists at http://www.eecis.udel.edu/~ntp/, for example.
After running ntpd for a little while your clock will be set to an accurate time and will maintain an accurate time. However, if the amount of difference is too great then ntpd will not modify the clock. After setting up ntp you can install ntpdate, ntpdate, ntpdate, ntpdate and on install (and reboot) the clock will be updated to the correct time according to the server you have chosen for ntp.
With ntp installed on one of your hosts, Velox for example, on the local network you can now use Velox as a ntp server simply by installing ntp on each machine and pointing them to Velox as the server.
Your donation will support ongoing availability and give you access to the PDF version of this book. Desktop Survival Guides include Data Science, GNU/Linux, and MLHub. Books available on Amazon include Data Mining with Rattle and Essentials of Data Science. Popular open source software includes rattle, wajig, and mlhub. Hosted by Togaware, a pioneer of free and open source software since 1984. Copyright © 1995-2022 Graham.Williams@togaware.com Creative Commons Attribution-ShareAlike 4.0