Ntpdate not updating
If your computer is connected to the Internet only for few minutes at a time, the network connection is often congested, you turn your computer off or suspend it frequently, the clock is not very stable (e.g.
there are rapid changes in the temperature or it’s a virtual machine), or you want to use NTP on an isolated network with no hardware reference clocks in sight, .
The optimal polling interval depends mainly on two factors, stability of the network latency and stability of the system clock (which mainly depends on the temperature sensitivity of the crystal oscillator and the maximum rate of the temperature change).
command usually reports a small number of samples retained for a source (e.g.
The switches should be configured to prioritize NTP packets, especially if the network is expected to be heavily loaded.
a computer without an RTC or virtual machine which can be suspended and resumed with an incorrect time) it may be necessary to allow the step on any clock update.
We have changed our policy so that general questions that would apply to both are acceptable here.
But I think this is one of those cases where it is a Raspberry Pi specific quirk.
So that is why it is resetting itself to 1970 everytime you boot the device.
The problem lies in ntpd's refusal to change the time if it is off by over a certain amount.
The example above would change to directive, the offset between the two reference clocks must be smaller than 0.2 seconds in order for the PPS reference clock to work.