[ntp:questions] ntpdate removal is coming
Richard B. Gilbert
rgilbert88 at comcast.net
Wed Dec 14 14:02:07 UTC 2011
On 12/13/2011 10:16 PM, unruh wrote:
> On 2011-12-13, Harlan Stenn<stenn at ntp.org> wrote:
>> Richard wrote:
>> [much elided]
>>
>>> Like it or not, NTPD, when started, will need up to TEN HOURS to
>>> settle down with the best time that you are going to get! This is not
>>> a hardship if you run NTPD 24x365 (366 in leap years). If you have to
>>> shutdown frequently and can't wait for NTPD to reach steady state then
>>> NTP is the wrong tool for you!
>>
>> You say this as if it is necessarily a bad thing.
>
> If it were the only way of ensuring good timing, it would not be. It is
> not. It is an extremely primitive feedback loop, which IMHO wastes a
> huge amount of information in the data. And the slowness of the settling
> down initially is just the other side of ntpd's poor handling of changes
> in the clock frequency ( due for example to heating because of the
> computer suddenly having to do some heavy computing).
>
You don't have to convince me. Dave Mills is the one to be convinced
and I'm inclined to believe that he knows what he is doing.
<big snip>
More information about the questions
mailing list