On 2009 Nov 18 (Wed) at 09:41:13 +0100 (+0100), Adrian von Bidder wrote: :On Wednesday 18 November 2009 02.01:42 Hal Murray wrote: :[pool command] : :I notice I've been quite out of touch, didn't know the pool command was :implemented :-) : :Just ccurious: I assume 'pool' is more or less a macro that takes effect at :ntpd startup? (I've been trying to find out with google, but it mostly :returns stuff relating to pool.ntp.org and not the pool ntp.conf command :-/ :) :
in OpenNTPD, we use 'servers' as a keyword for this feature. We try to syncronize to all of the servers that are returned (be it 5, or 10, or whatever). :Or is a 're-do the lookup after n of the m pool servers are offline for at :least k days' style of thing already implemented? Because when I use 'pool' :to specify the server, I'm saying 'I don't care what ntp server actually is :being used, just make sure there something sensible', so I don't see any :reason why anybody would wish the list to be static. : I have a longish running session of OpenNTPD with three 'servers' lines, and 16 of 16 are valid. We don't yet relookup dns names if we've had many failures, though. Thankfully, this seems like it wouldn't be that critical of a feature. :(I realize this might not be trivial to implement within the current ntpd :codebase...) : :cheers :-- vbi -- When you try to make an impression, the chances are that is the impression you will make. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
