Still working out the issues with the crashing but this is a new
question so a new thread.
Here is the peer list from ntpq. My question is, what has determined
that the remote peer 130.207.165.28 is the best one to sync against even
though it has the worst offset and jitter. It consistently stays this
way no matter how long ntpd is running.
remote refid st t when poll reach delay offset jitter
==============================================================================
-69.36.227.90 69.25.96.13 2 u 404 512 377 35.574 -0.367 0.449
-169.229.70.95 128.32.206.55 2 u 463 512 377 39.506 -1.586 0.376
+208.87.221.228 10.0.22.51 2 u 401 512 377 37.755 2.173 0.249
*130.207.165.28 130.207.244.240 2 u 414 512 317 82.198 4.112 0.637
-131.144.4.10 65.212.71.102 2 u 363 512 377 84.720 1.632 0.589
o127.127.22.1 .PPS. 0 l 11 16 377 0.000 0.006 0.061
+127.127.28.0 .GPSD. 0 l 42 128 377 0.000 4.229 10.549
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions