On 23/02/17 00:04, Arnold Schekkerman wrote: > All you do with multiple monitoring servers is check more routing options. > The only > logical thing to do is to reject the server from the pool as soon as it is > unreachable via at least one route. From our client's perspective this would > make > the pool more reliable. However, even more servers will see their score > drop... > > Please, keep in mind the monitor is NOT about checking if a server knows the > correct time. It is about checking if a server (with correct time) is able to > *provide* that time to a client connecting to it from just anywhere on the > internet > using the DNS system.
Exactly, this. Multiple monitoring should reject more servers. Because really if you have a server that is connected to an ISP with routing problems, then I think that server shouldn't be in the pool. I guess it is hard to accept that your score is low because of your ISP or even your ISPs upstream connectivity. Even when you know you have done everything correctly. A different problem is a good way to investigate these kind of funnies and try to work out what is going on and what the real problem is. -- Tim Bray [email protected] | +44 7966 479015 | http://www.kooky.org Huddersfield, UK _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
