On 28-01-07 23:58, [EMAIL PROTECTED] wrote: > As a conclusion for our little survey, I would say only 2 main ideas > came up ( new DNS lookups, and spare servers ) and that both should be > implemented judging by the views of the pool server admins on this list.
Agreed. However, when looking back at the 'problem' of the OP (incoming traffic after being out of the pool for some time) I guess the first idea (new DNS lookup) has priority over the second for the following reasons: - Admins using the pool will most likely use the pool for spares too (but perhaps regions as main, and global as spare instead of both the same), so a spare would basically be a new DNS lookup. - We want traffic to go away. Traffic caused by admins that don't look after their NTP after installation. I cannot believe these admins will bother reconfiguring ntpd to configure spares, so spares will not help us. - Why should an admin ever want to configure a spare if he can configure a real server as well? So I guess we are looking for solutions in ntpd only; not for additional options in the already complex (or feature rich) ntpd configuration. BTW Funny to see how most discussions sooner or later evolve to 'auto optimum configuration' solutions :-) Arnold _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
