Rob van der Putten wrote:
Hi there
Martin Burnicki wrote:
This indicates that either the NTP daemon itself, or its upstream server(s),
may not have received the leap second announcement, and so time
synchronization has been messed up.
<snip>
I was hoping that one could piece together exactly what has gone wrong.
Right now I don't think that this is ever going to happen.
The only way that one can avoid these problemes is probably to use ones own
GPS receiver instead of somebody elses NTPD.
Don't count on it! The Motorola Oncore driver in nptd 4.2.0 failed to
handle the leap second correctly. There was a bug logged in Bugzilla
and a patch was available but if there was an announcement, I missed it.
It looks as if about half the world fumbled the leap second somehow!
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
