I haven't had any off-list replies to summarize.
[email protected] said: > You mean that the latest stable release still doesn't support this? I don't think the pool command is very useful in the stable release. It's been totally re-written in the last year or so. > And 0.debian.pool.ntp.org only gives me 3 IP addresses. The answers returned by the pool servers have a short TTL. They get rotated quickly. ntpd will use what it gets, then try again, occasionally, until it gets enough unique working addresses. Addresses that don't respond get dropped. During startup, it may add more than it needs if some of the ones added recently haven't responded yet. The extras will get dropped. > But I don't see the point of more than 5, specially if ntpd tries to remove > the bad servers itself. I don't think that ntpd currently removes "bad" servers. I think it dumps servers that don't respond and then gets new ones. It seems like a good idea to do something like drop the worst server every day or hour and see if you can find a better one. ntpd doesn't do that yet. > Does that also mean that people could potentionally hang during boot because > the pool command is still trying to find servers, and some services are > waiting for ntpd to say it's started? It means it won't start as fast as it could. -- These are my opinions. I hate spam. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
