[ntp:questions] Re: ntp sanity limit kills ntp daily

Douglas Mayne doug at slackware-3.localnet
Mon May 23 16:05:50 UTC 2005

On Fri, 20 May 2005 11:55:10 -0700, Michael Ward wrote:

> Hello All,
> I've configured my FC3 system to run ntp successfully at boot time and 
> ntp seems to run successfully for about a day.  However, every night the 
> clock looses some 1200 seconds while the system is busy making backups. 
>   When ntp figures this out, it refuses to update the clock because this 
> is classified as insane, and terminates.
> I happen to agree that the clock loosing about 1200 seconds (for any 
> reason) seems insane.  However, given that this sort of behavior seems 
> common enough to be found via google (search for: ntp exceeds sanity 
> limit), I'm hopeful that there is a way to coax ntp (or some other 
> automated program) to trudge on and do the deed anyway.
> Default rules can make is seem like a crazy world, can't they?
> I'm running a self compiled linux kernel 2.6.9 with FC3 linux as 
> installed from Negus' "Red Hat Fedora Linux 3".  Anyoune out there know 
> how to make this sort of thing work in a rational manner?
> Thanks.
> - Mike
Caveat: I am not running FCx (or Red Hat).  I do know the database for
the locate command is rebuilt at some time interval and I have
noticed high CPU utilization when this occurs. If your backup operation is
on the same schedule as this database refresh, then the system may be
pushing its limits. This is especially true for older CPUs on 2.6.x. What
is the speed of your CPU?

Does the clock lose time when using a "stock" Red Hat kernel?

More information about the questions mailing list