[ntp:questions] step and stepout
Edward T. Mischanko
etm1962 at hotmail.com
Sun Jun 30 22:46:51 UTC 2013
"Orna Sumszyk" wrote in message
news:CAGy55tPi8waAuAjsaX3ZGh9JeuT2VMYHUFiqzcTdDY5QA-LP3g at mail.gmail.com...
in my ntp.conf file i write the following sentence:
tinker step 0.01 stepout 1
How can i verify that the ntp algorithm is really behaving following this
command, i.e. stepping only one second after it pays attention to the fact
that the offset with the server is above 10 msec?
By the way, could i write
tinker step 0.01 stepout 0
so that the step is performed immediately when the offset is above 10 msec?
What you write should work, but stepping the clock is not the preferred
method of control.
Slewing the clock causes less file system problems.
tinker [allan allan | dispersion dispersion | freq freq | huffpuff huffpuff
| panic panic | step step | stepout stepout]
This command alters certain system variables used by the clock discipline
algorithm. The default values of these variables have been carefully
optimized for a wide range of network speeds and reliability expectations.
Very rarely is it necessary to change the default values; but, some folks
can't resist twisting the knobs. Options are are as follows:
step step Specifies the step threshold in seconds. The default without this
command is 0.128 s. If set to zero, step adjustments will never occur. Note:
The kernel time discipline is disabled if the step threshold is set to zero
or greater than 0.5 s. Further details are on the Clock State Machine page.
stepout stepout Specifies the stepout threshold in seconds. The default
without this command is 300 s. Since this option also affects the training
and startup intervals, it should not be set less than the default. Further
details are on the Clock State Machine page.
More information about the questions