NTP and Leap seconds
-
Hello fellow Netgate community members,
Does anyone have any other recommendations on how to load leap seconds for very accurate time?
I have loaded them into the advanced NTP options here
Ref:
https://www.ietf.org/timezones/data/leap-seconds.list
(Image: Text based leap second load)
(Image: Leapsecond loads) -
(IMAGE: Time shows good load however shortly after shows Unsynchronized) -
According to freebsd kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized everything is fine.
Before ntpd starts, your local time will be 'incorrect', like a second or so off.
Except if the local RTC is also a stratum 0 time server ;)Btw : I've uses your 'leap second file', and I saw the same message.
My pfSense clock look fine. -
Yes, that is always reported when ntpd starts. It's not a sign of any sort of issue at that point.
Steve
-
@stephenw10 thanks for the reply, I was thought it meant that it overrides my leap seconds. But that is not the case. I can see the offsets under services ntp
-
@stephenw10 is the file essentially the same as the text based advanced option?
-
I've never tried that. But I'd say you're doing it correctly since the logs are reporting the file was loaded as expected.
