2010-01-15
I upgraded ntpd on ntp.cs.uu.nl from 4.2 ...
I upgraded ntpd on ntp.cs.uu.nl from 4.2.4 to 4.2.6 and suddenly I notice in the output that this has changed the stratum from 2 to 1.$ ntpq -c rv ntp.cs.uu.nl status=011d leap_none, sync_atomic, 1 event, event_13, version="ntpd 4.2.6@1.2089-o Fri Jan 15 14:31:14 UTC 2010 (1)", processor="i386", system="FreeBSD/5.4-RELEASE-p13", leap=00, stratum=1, precision=-19, rootdelay=0.000, rootdisp=1.456, refid=PPS, reftime=cefb066f.cbe638ff Fri, Jan 15 2010 16:21:19.796, clock=cefb0693.889dd5ee Fri, Jan 15 2010 16:21:55.533, peer=7047, tc=6, mintc=3, offset=-0.001, frequency=15.448, sys_jitter=0.002, clk_jitter=0.001, clk_wander=0.002Which matches the peer list where the PPS stratum is now 0:$ ntpq -c peer ntp.cs.uu.nl remote refid st t when poll reach delay offset jitter ============================================================================== *huygens.cs.uu.n .PPS. 1 u 23 64 377 0.197 0.009 0.258 +stardate.cs.uu. .PPS. 1 u 13 64 377 0.998 -0.058 0.033 +tijger.phys.uu. metronoom.dmz.c 2 u 15 64 376 0.599 0.004 0.185 LOCAL(0) .LOCL. 10 l 627 64 0 0.000 0.000 0.002 oPPS(0) .PPS. 0 l 49 64 377 0.000 -0.002 0.002 NTP.MCAST.NET .MCST. 16 u - 64 0 0.000 0.000 0.002I guess some definition of PPS input has changed. Now I wonder how much more ntp traffic this will cause.