On 6/30/2012 17:09, A C wrote:
It appears that my system did not respond well to the leap second.
The GPS has not yet received the leap second notification via the
satellites (it is currently still reporting an offset of 15 seconds).
The leap second was inserted by ntpd according to the leap file and then:
[snip]
Previously the Internet servers were only a few milliseconds offset but
SHM(0) showed +1030 or so seconds offset.
The GPS finally recovered, reporting the new offset almost eight hours
after the fact. However, ntpd was not happy with this situation at all
during that period. The clock was stepping back and forth by a second
because the GPS disagreed with five Internet servers.
It has settled down again though it appears that one server I use didn't
step its own time. It shows as having a one second offset but that's
not an issue I have to handle.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
