[ntp:questions] Re: Ntp-4.1.2: tinker step 0; always slew and kernel time discipline

David L. Mills mills at udel.edu
Fri Feb 18 02:27:03 UTC 2005


Tom,

The -x option simply sets the step threshold to 600 s. This on the 
assumption that a network of critters with greater tolerance probably 
doesn't need ntpd at all. Just set the clock by eyeball-and-wristwatch 
and be done with it.

Dave

Tom Smith wrote:

> Nikolaev, Sergey wrote:
> 
>> We have a requirement to always slew the clock even if it means long 
>> periods of time to correct the offset.
>>
>> The NTP documentation mentions this tinker option:
>>
>> step step The argument is the step threshold, by default 0.128 s. It 
>> can be set to any positive number in seconds. 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 the 
>> default.
>>
>> However when I set "tinker step 0" and restart ntpd, I see in "ntpdc 
>> -c sysinfo" that the kernel flag is still enabled.
>> Obviously, it is not disabled automaticly just by setting "tinker step 
>> 0".
>>
>> Do I need to disable it explicitly?
>> Thanks in advance,
>> Sergey
>>
> 
> Not a direct answer to your question, but it sounds like what you really
> want to do is instead start ntpd with the "-x" flag.
> 
> -Tom



More information about the questions mailing list