In light of David's report and looking at my own similar Windows ntpd + PPS GPS setup, I retract my "nuanced" comments about his offset graph, because I now believe ntpd on Windows misapplied the leap second completely. The code scheduled it perfectly, relayed the info on to clients correctly, then at the moment of truth disarmed the leap indication on schedule, then went on to consider applying it, and decided not to as it was no longer armed. Oops.
It apparently took 12.5 minutes for the receiver to apply the leap second, between these two clockstats entries: 56109 735.330 127.127.20.1 $GPGGA,001213, 56109 753.320 127.127.20.1 $GPGGA,001232, 735 - (12 * 60 + 13) = 2s 753 - (12 * 60 + 32) = 1s Leap seconds are exciting. Cheers, Dave Hart _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
