[email protected] said: > 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 :-/
Yes. It's just like the server command except that it uses up to 10 IP Addresses from the DNS name lookup. After that, it doesn't do anything fancy. It just keeps on using those servers as if they were each added with a server line. Various enhancements are possible. I don't think anybody is working on them. One would be to occasionally (daily?) replace the least-good server with another one from the pool. If all clients implemented that, it would be possible to take a server out of the pool in a day or so. The pool command has been in ntpd for quite a while. It works in the normal case, but it doesn't (yet) work if the DNS lookup doesn't get an answer when ntpd reads the config file. (If that happens, ntpd sets up a separate process to retry the DNS lookup occasionally. That process didn't get the pool vs server info.) After we get this all sorted out, the typical ntp.conf file should be as simple as: pool whatever.pool.ntp.org -- These are my opinions, not necessarily my employer's. I hate spam. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
