On Monday 22 August 2005 04.14, [EMAIL PROTECTED] wrote: > Pick a couple of reliable NTP servers in each area, have them ping > everyone nearbywith minpoll 1024, and you can suck your statistics out > of the loop filters. > > In fact, judging by old mailing list traffic about monitoring servers, > that's pretty much exactly how it's done...
If you mean 'how server quality was measured for the scoring algorithm of pool.ntp.org', then that was only in the very beginning. ntpd quickly gets unstable (time jumps around a lot) when there are more than 50 or 100 servers configured, so I'd have needed a pretty large monitoring server network. Lazyness made me not pursue this, changing to 'ntpdate'-type single requests without all the fancy statistics that ntpd does. As was said, I regard the pool as a way to easily access some approximation of the True Time)tm), not as a way for precise timekeeping. cheers -- vbi -- featured product: the GNOME desktop - http://gnome.org
pgp69dcql4uI4.pgp
Description: PGP signature
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
