On Thu, 25 Jan 2007, Tony Hoyle wrote: > Anything that requires config file changes basically isn't going to be > implemented by 99% of admins & won't solve anything in the short/medium > term. Remember these are mostly people who've used the default pool.org > in their config and probably think that covers them forever. > > I like the idea of having a backoff to 24 hours. Solves a lot of > traffic problems (not just pool ones) and is probably a simple change. > > Fresh DNS lookup can't really be got around for pool use - I suggest > after a server is down for 24 hours (and every 24 hours after that? Or > every 7 days? DNS fails sometimes too...) > > Tony
Very good point. New DNS lookups might indeed be a better solution. That's what we are debating after all ;-) It would also open the door to more dynamically hosted ntp services with servers IPs in the pool for only a few months or so. But set aside change to the configuration file ! Much worse, a new installation of ntpd will be required. I think active and spares configurations could be bundled with the new ntpd version or the patched one. Patched ntpd could come with a default pool config file including active and spares. Of course, making new DNS lookup is a more transparent solution, so let's see what Guillaume who kindly volunteer to write the patch chooses to do ;-)) -Louis _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
