On Sat, Feb 11, 2012 at 09:42, A C <[email protected]> wrote: > On 2/11/2012 01:21, A C wrote: > > This is the more recent status though I'm not sure why the PPS is marked as > bad. > >> remote refid st t when poll reach delay offset >> jitter >> >> ============================================================================== >> x127.127.22.0 .PPS. 0 l 5 16 377 0.000 0.002 >> 0.122 >> 127.127.28.0 .GPSD. 4 l 84 128 377 0.000 -30.840 >> 15.522 >> +69.65.40.29 209.51.161.238 2 u 36 128 377 74.436 1.585 >> 0.199 >> -169.229.70.201 169.229.128.214 3 u 111 128 377 37.326 3.009 >> 0.571 >> +198.137.202.16 69.36.224.15 2 u 111 128 377 36.641 1.851 >> 0.400 >> *130.207.165.28 130.207.244.240 2 u 95 128 377 78.266 1.667 >> 0.736 >> -131.144.4.10 130.207.244.240 2 u 40 128 377 85.358 3.798 >> 1.243
See http://www.eecis.udel.edu/~mills/ntp/html/cluster.html with the understanding that falsetickers (x in peer tally code in first column) are those pruned by the cluster algorithm. Cheers, Dave Hart _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
