Tim Lundstr?m <[EMAIL PROTECTED]> wrote: > Sometimes one have to switch off the NTP server or service for different > reasons such as planned maintenance, during thunderstorms or for > internal testing. However, the server is still included in the pool > until the score drops below 5. This means that a non working server is > included for some time. Then, when the server goes online again it takes > a while until it is included in the pool again. My feeling is that it > would be much more efficient to make it possible to mark a server as > unavailable during planned outtakes. When manually marked unavailable, > the server is immediately taken out of the pool but the score is kept. > When marked as reachable again, the server goes into the pool whith the > same score as before the outtake and normal selection rules is applied. > > What do you think? Is this a good feature and is it possible to easy > implement it in todays structure?
It's a "not necessary" feature. Most (all?) clients will allow multiple servers to be named. Good clients do real-time monitoring of their own which is going to be superior to centralized scoring/DNS in every possible aspect. There are some "bad" clients which, when they don't get a response back from a server, increase the polling rate on the non-responding server. Not much can be done about these hosers though. Tim. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
