ntp_adjtime and interval

[Miguel Gonçalves]

Hi!

I am trying to figure out why NTP takes so long to react to oscillator
changes...

When checking ntptime on startup I see that the NTP daemon is using
PLL and starts the adjustment interval at 8 s. It then increases to
16, 32, 64, 128 and stops at 256.

I read in the documentation that this limit should be 128 but is now 256.

--- start from http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm ---
intervals 57 says that there were 57 calibration intervals. When PPS
pulses are arriving, this number should increase. Each frequency
adjustment requires a good calibration interval. The length of the
current calibration interval can be found as interval 128 s (128
seconds is the default maximum length). Remaining numbers count
abnormal conditions as explained below.
--- end ---

How can I make it stop earlier? At 64 s for example?

TIA,
Miguel

[Nickolay Orekhov]

You should use "maxpoll n" option. The length of the intervall will be 2^n
seconds.
Example configuration file should look like this:

server 192.168.0.2 maxpoll 3



2013/5/15 Miguel Gonçalves <miguel.barbo...@gmail.com>

> _______________________________________________
> questions mailing list
> ques...@lists.ntp.org
> http://lists.ntp.org/listinfo/questions
>
>

[E-Mail Sent to this address will be added to the BlackLists]

Nickolay Orekhov wrote:> You should use "maxpoll n" option. The length of the

> intervall will be 2^n seconds.
> Example configuration file should look like this:
>
> server 192.168.0.2 maxpoll 3

Which would be fine for local refclocks, and your own servers,
but perhaps considered abusive for others servers.


--
E-Mail Sent to this address <Blac...@Anitech-Systems.com>
will be added to the BlackLists.