On 2/25/2012 5:05 PM, A C wrote:
On 2/25/2012 13:09, Richard B. Gilbert wrote:
On 2/25/2012 1:20 AM, A C wrote:
On 2/24/2012 21:26, A C wrote:
Is it possible to change the polling interval of one or more
associated
servers at runtime? It seems like I should be able to run:
ntpq -c "writevar &associd hpoll=N" or is it ppoll?
Actually, I should have been more specific and say change the minimum
polling interval. In other words, be able to adjust the conf file's
minpoll flag at runtime instead of restarting.
What problem are you trying to solve?
NTPD does a pretty good job of adjusting itself most of the time.
Short poll intervals are useful when correcting large errors.
Long poll intervals allow NTPD to make small corrections very
accurately.
The idea was to bump up the minimum poll interval after ntpd has been
running for a day or so to something more kind to the remote servers
because the refclock is holding the remote servers clamped to 64
seconds. If I set minpoll in the config file, then ntpd's start up
takes a long time because of a long poll interval. If I don't set the
minpoll, then ntpd doesn't do "a pretty good job" because it clamps
the polling interval.
I've noticed the same thing. You could try what I'm doing, although I'm
still testing for the best configuration.
# GPS Lines
server 127.127.20.5 prefer minpoll 3 maxpoll 6 mode 72
fudge 127.127.20.5 time2 0.3100 refid GPS1
# Internet server lines
# NIST New York
server nist1-ny.ustiming.org minpoll 8 maxpoll 13
# other internet server lines similar
Sincerely,
Ron
--
(PS - If you email me and don't get a quick response, don't be concerned.
I get about 300 emails per day from alternate energy mailing lists and
such. I don't always see new messages very quickly. If you need a
reply and have not heard from me in 1 - 2 weeks, send your message again.)
Ron Frazier
timekeepingdude AT c3energy.com
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
