>> The problem is that it doesn't support the "noselect" option when >> adding a peer: >> http://fortytwo.ch/mailman/pipermail/timekeepers-dev/2007/000006.html > > Right.
Of course, this could be easily added to ntpdc. >> I can't remember why we needed it thought... > > 1) We can't use the monitored servers to set the time on the monitoring server. Right, which could be done with noselect. > 2) ntpd doesn't deal nicely with a thousand servers in the selection algorithm. But if noselect is specified, would the algorithm still have a problem with so many servers? I still think that something better could be done in the monitoring, particularly with regards to pruning more aggressively those servers more likely to end up at the top of the pool. After all, they kind of set the standard for the pool and having underperforming high-bandwidth servers as 63.240.161.99 make the pool look bad. Thanks. -- __________________________________________________________________ Evandro Menezes Austin, TX http://themenezes.us _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
