[time-nuts] Holdover, RTC for Pi as NTP GPS source

Chris Caudle chris at chriscaudle.org
Wed Nov 1 16:57:05 EDT 2017


On Wed, November 1, 2017 3:17 pm, MLewis wrote:
> hadn't got there yet

Your RTC is not likely to be tightly synchronized to NTP time, so there is
a high probability that trying to use RTC as a secondary time source will
actually make the system worse than just riding through using the NTP
estimate of the current system clock frequency.  If ntpd will even use it
as a secondary clock, and not reject it because it is too far off from the
preferred GPS source.

Is this system not connected to other NTP servers over the network? 
NTPsec does not work very well in the case of only one GPS device
available to set time, that is documented as one of the use cases which
NTPsec does not currently handle well.  If there are no other servers
available for comparison you will probably want to use chrony.  If there
are other servers available then trying to switch over to the RTC will
definitely make your ntp server perform worse than just leaving well
enough alone.

-- 
Chris C




More information about the time-nuts mailing list