>Actually, one of the things we're looking at is implementing a >"servers" directive. The idea being that you take all of the IP >returned by the DNS for a given label, and sets up unicast >client/server relationships with *all* of them.
Hey, that's a good idea. ntpd is already figuring out which clocks are best from a big list; just give it a big list from pool.ntp.org and let it figure out which one is closest / best time. The only drawback I see here is that if we recommend this as a default, the traffic from each client goes up a lot. Maybe there's a way to get the servers implementation to choose just 3-4 servers after a few hours? Has anyone collected statistics on which client software people are using with our pool? _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
