[ntp:questions] Re: minpoll and maxpoll
srui at fe.up.pt
srui at fe.up.pt
Tue Dec 21 15:15:21 UTC 2004
Dear NTP mailing list users,
I am running a NTP server on an mobile network without regular Internet access
and I use a GPS (which is always available) to correct the system clock through
NTP. Sometimes the system has to be shutdown and the hardware clock just isn't
good enough to keep time between power cycles. In a normal situation with a big
clock skew the NTP daemon crashes, so I was told that using a low value for
minpoll would solve this and it would be the correct equivalent to a forced
initial correction. Is this true? What solutions do I have for this?
Sergio Rui Silva
Citando "Richard B. Gilbert" <rgilbert88 at comcast.net>:
> Helmut Wollmersdorfer wrote:
> > Yesterday I specified
> > minpoll 6 maxpoll 8
> > for my local references, but no explicit values for the remote, public
> > timeservers in /etc/ntp.conf.
> > Now, 11 hours after restart, the actual values for poll in
> > ntpq -p
> > show no value higher than 256.
> > As I remember poll went very fast to 1024 without any minpoll or
> > maxpoll in the config.
> > As I do not want to produce to much traffic on public servers, shall I
> > specify something like
> > minpoll 8 maxpoll 10
> > for them?
> > Helmut Wollmersdorfer
> You should not specify either minpoll or maxpoll without very good
> reason! Minpoll defaults to 6 and maxpoll to 10 giving a range from 64
> seconds to 1024 seconds. The daemon will adjust the polling interval
> within this range as needed. The longer polling intervals are needed to
> let the code "fine tune" your clock.
> questions mailing list
> questions at lists.ntp.isc.org
----- Finalizar mensagem reenviada -----
More information about the questions