On 2013-02-24T17:30:01-0800, Hal Murray <[email protected]> wrote: > Harlan is getting ready to release the next version of the standard NTP > package. The pool command seems to work. How many of you are testing it?
The pool command works great for me. > I think clients using the pool should occasionally check to see if an address > they picked is still in the pool and pick another one if it has dropped out > of the pool. (or at least stop using the old one) > > Is there a way to do that? I assume it would use DNS. > > How are we going to test this? Would it be reasonable to setup a batch of > systems that are already in the main pool and put them in something like > test.pool.ntp.org, and rotate them in/out fast enough so it would be easy to > test? Say in for an hour, then out for a few days. 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. -- Kenyon Ralph
signature.asc
Description: Digital signature
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
