[email protected] said: > The pool command works great for me. Thanks. I'm slightly surprised that nobody else has responded. If people respond to me off-list, I'll summarize in a few days.
[email protected] said: > Why would you do this? If the pool monitoring system reduces the score of a > pool member because it's unreachable or providing bad time, then an ntpd > configured with the pool command will stop using that server too, if it sees > that the server is poor, right? No need to check whether the server is still > in the pool system. As Ask pointed out, I was looking for a polite way to extract a system from the pool without having to turn it off. ntpd servers don't know anything about the pool monitoring. That monitoring just keeps not-good servers from being announced via DNS so new inquiries won't use them. If a server stops responding, ntpd will discard it and try to get another one. Thanks for pointing out that if you do turn a system off, the current code will stop using it. I was so focused on leaving the system on that I hadn't thought about turning it off. That's not great, but I think it's good-enough to ship. -- These are my opinions. I hate spam. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
