I just looked... and it has a score -26.9 because it was offline for a number of hours (but is now back.) On Friday/Saturday I see it bounce around a lot but that has everything to do with network latency I bet, and little to do with whether the server has right time or not (I note that the average time seemed good throughout).
Different people have different standards for "high offset". Some will object to something 3 milliseconds off even though the network latency is ten times that. Ntpd itself has a different (and IMHO superior) set of criteria than what is used in the pool but a good ntpd configuration has at least 3 servers so the bad ones can be out-voted, and it also looks very crucially at latency... and because a good ntpd config has at least 3 servers it can afford to be ultra-picky when multiple good servers are available. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jos van de Ven Sent: Monday, June 07, 2010 9:44 AM To: NTP Pool list Subject: [Pool] Server offset high but still in pool Please look at the graph of this server: http://www.pool.ntp.org/scores/109.72.80.61 It has a score above 10 but I think it is behaving very bad (probably on a virtual box) and treated as an outlier. My opinion is that this server should not be in the pool, which means should have a score below 10. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
