Mike Cook wrote:
< snipped>
The server was still in the peerstats at 18:25 the following day
when I did a reboot. So, after approximately 27 hours, ntpd hadn't
dropped it. Obviously, my system isn't performing as you say it
should. Can you, or anyone else, provide a clue as to how I might
determine if my system is a fault or if there is a bug in the ntpd
code?
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.
Hmmm. Sometime back I had noticed on my servers using the pool, that
a couple of the selected servers had stopped responding. I did not
know at the time that that situation was supposed to be dynamically
corrected so I dropped the pool as being unreliable. Maybe there is
some issue. I just re-configured 4 servers back to using the pool and
will monitor for black sheep.
You have to use the 'pool' instead of 'server' command in order to get
the automatic inclusion of multiple servers, with automatic monitoring
and pruning.
When I first tried 4.2.8 I noticed the "soliciting" lines and that
occasionally a server didn't get used.
I have that too.
Could this also be because you don't have enough servers in your pool?
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
