Rob wrote:
Roger <[email protected]> wrote:
http://www.pool.ntp.org/scores/90.155.73.34
How does one alert an operator that their server is sick?
Checking back through my peerstats I see that last entry
which was okay was 2015-02-16 15:08:56.
There is no need. The pool system has sent a mail to the operator
and when he apparently does not react it is not a problem because
the server will have been removed from the pool anyway.
You are of course correct, I would just add a single small caveat:
If you are using an older version of ntpd which doesn't support the pool
directive, then you would be stuck trying to access such a server until
you restart ntpd.
With something like 'pool pool.ntp.org' in your ntp.conf file the ntpd
process will pick the first N (10) servers returned from DNS, then once
every hour it will redo the DNS lookp, the two worst-performing current
servers will be removed and a pair of new ones will be used to replace them.
I.e. as long as you use the pool properly there is no need to worry
about servers coming and going, or even individual servers that become
falsetickers.
Terje
--
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
