Whoops, opined on the wrong server :-). 109.72.80.61's only problem seems to be jittery and asymmetric network latency. I betcha it knows the right time all the time - it's just that the network connection to it has intermittently high latency, and that latency appears to be one-way.
Ntpd uses latency (on a response-by-response basis) when determining whether to use a server or not so I don't see any reason to throw 109.72.80.61 from the pool. Tim. -----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
