Brad Knowles wrote:
We're not here for the people who are trying to tweak the last
nanosecond out of their clock. We're here for the people who want to
make sure that their clock is at least accurate down to the second, and
anything beyond that is gravy -- but they need to keep in mind that they
might not get gravy next time.
I imagine use like:
"Bert, the webserver is three minutes fast again."
$ sudo ntpdate pool.ntp.org
"It's fixed Ernie."
And the software distributors that can ship a working ntp.conf:
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
Anything more than that is gravy. The <region>.pool.ntp.org domains are
only for the people that care to read the NTP documentation. 98% of the
computer users is/would be happy when the computer clock "automagicly"
is correct (within their observation error of one minute).
It's more important to spend time on finding more servers to share the
load than to try to solve the "Internet topology problem". Sorry, just
my opinion.
Greetings,
Peter.
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
