ntp frequent time resets - battery dead?

[Charles Swiger]

Hi--

On Mar 12, 2014, at 12:26 PM, Anton Shterenlikht <mexas at bris.ac.uk> wrote:
>> Yes, it looks to be about ~1 second per hour.  That's 1:1000 ratio,
>> which is getting close to the typical kernel limit on adjtime().
>> 
>> Tweaking the step threshold might help.  Or look into tickadj / ntptime.
> 
> Sorry, I don't understand this.
> Please elaborate.

OK.  ntpd has two ways of adjusting the clock; either it gradually slews the time
via adjtime() or it jumps the clock via settimeofday() and logs the "time reset"
lines you've noted.

Which method is chosen is based upon the step threshold, which defaults to 128 ms
(aka .128 seconds).  Increasing the step threshold will have ntpd try to slew
the clock even for the larger corrections your case seems to need.

Regards,
-- 
-Chuck