Miguel Gonçalves wrote:
Hi Dave!
Thanks for all your help!
2011/10/13 Dave Hart <[email protected]>:
Likely nothing. I would watch the memory consumption by ntpq for a
hint of what is going on, or try it adding one or more -d options to
the ntpq command line to see exactly what's happening. Hopefully with
enough patience it will complete, but it is challenged on busy
servers.
It took quite a while but in the end I used
/usr/local/sbin/ntpq -c "mrulist mincount=10 sort=avgint"
and it returns much quicker.
I also added the "kod limited" to restrict command because I was
seeing some clients do this
lstint avgint rstr r m v count rport remote address
==============================================================================
10 15 590 K 3 3 375 3947 88.210.126.56.rev.optimus.pt
1104 15 590 K 3 3 210 3693 pa7-84-91-194-235.netvisao.pt
366 15 590 K 3 3 125 4354 pa-217-129-49-198.netvisao.pt
254 15 590 K 3 3 293 4622 81.84.253.49
(a81-84-253-static.cpe.netcabo.pt)
I thought: what the hell? Pooling every 15 secs? These are real time-nuts! :-)
It can also be a gateway for an internal network with your
server being polled by all the clients on that network.
David
With KOD this seems to have stopped.
By the way, I am using 4.2.7p222. Is this stable enough for a pool server?
Cheers,
Miguel
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
