Do you know what time it is? Relative to what? Regardless, it's always good to have a local NTP server in your network and there are a couple of ways you can go about this. For background, NTP server's calculate their accuracy based upon how far away they are from a source of truth. Consider the clocks at NIST and other locations being the center of the bullseye: 0. Anything that get's their time check from them becomes +1, and so on, so forth. The name for this distance is called "Stratum", and would be described as "Stratum-0" for the source, and after a few hops, "Stratum-4". As you can imagine, the further away you get from the source, the more you drift from the true time value. For 98% of us, this doesn't matter, but there is a cult in this space; so be warey traveler, you should be simply stasfied as 'apt-get install ntp'.
If you want to begin the journey of exploring and having better local time sources, because why not, you should consider purchasing or building a NTP server that uses GPS sync for its Stratum connection; the benefit here is that it will work without the Internet.
If you would like to go the DIY route, there are plenty of examples of using a RaspberryPi with a GPS hat that has a PPS output, and the ability to talk to NTPd. If you don't go the route of not using a RaspberryPi and a hat, look for a USB adapter that has PPS. So, what's with this "PPS" requirement? It stands for "pule per second," and GPS's that will work as a time source will send this clock pulse, once per second, for NTPd to detect and calibrate against.
|