On Wed, Dec 31, 2008 at 1:48 PM, Martin Radford <
[email protected]> wrote:
> I predict confusion.
Well, my server is doing something funky since the leap second!
remote refid st t when poll reach delay offset
jitter
==============================================================================
+time.nrc.ca 132.246.168.3 2 u 320 1024 377 30.004 -13.748
0.524
+ecmail2.cmc.ec. 142.135.6.200 2 u 564 1024 377 26.665 -14.381
0.078
LOCAL(0) LOCAL(0) 10 l - 64 377 0.000 0.000
0.001
*SHM(0) .GPS. 0 l - 16 377 0.000 -2.438
3.006
SHM(1) .PPS. 0 l 154m 16 0 0.000 0.000
4000.00
Looks like NTPD has started to reject the PPS signal since the leap, but
loves the NMEA output (which, oddly enough seems to be quite stable!). I
wasn't around to see what happened at 0000UTC, but I suspect that NTPD
rejected the PPS from my GPS post leap time for some reason. Probably
because of how GPSd is handling the connection to the GPS. It'll be
interesting to see the logs when I get back to the office....
If these message gets to you, then I suspect the leap second didn't kill the
Internet!
Happy new year.
-Rob
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
