In <1063211368.30336.4.camel@bohr> Anthony DeRobertis <asd@???> writes:
> On Wed, 2003-09-10 at 11:41, wayne wrote:
>
>> Long or erratic network delays can also flag a ntp server as being a
>> false ticker even when it is keeping good time. These network delays
>> will cause the ntp server to be useless to everyone else, but not a
>> problem for them.
>
> Those network delays may or may not cause a problem for them. If they're
> trying to synchronize over that crazy network, it'll certainly cause a
> problem.
Yes, I should have been a little more careful with what I said.
> I think if someone volunteers their server for network time
> syncrhonization, and it turns out their server, network, whatever is not
> suitable, we should tell them. It's not like we're going to send them a
> message every hour saying "your time server is giving bad time."
> Instead, it'll probably be one message, once only. And it'll probably be
> checked from multiple places around the globe.
I'm suggesting that a few QA servers monitor the quality of all ntp
servers in the pool and any that are currently not healthy enough
should not be selected for the round-robin DNS server. I would expect
that most ntp servers would, from time to time, not make the cut. I
don't think we want to warn people every time this happens. Only if
an ntp server regularly fails to make the cut should a message to this
list and/or the admin be sent.
Someone suggested a web page of ntp server status, and I would think
that would be a good thing to have.
-wayne
_______________________________________________
timekeepers mailing list
timekeepers@???
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
