[ntp:questions] Re: Another time kernel 2.6 and ntpd.

Richard B. Gilbert rgilbert88 at comcast.net
Wed Jan 28 23:29:13 UTC 2004

It could be that your local clock is drifting faster than ntp can 
correct it.  I believe I recall reading here that 500 ppm is the maximum 
drift that ntp can correct.  If it's worse than that you need to do 
something with tickadj to fix it.  I have never done it myself, or 
needed to, so you'll need to get the details from someone who knows how.

Ruben Navarro Huedo wrote:

>WARNING: Unsanitized content follows.
>Hash: SHA1
>This is what i can see in syslog running ntpd under kernel 2.6:
>Jan 28 22:47:56 linux ntpd[28795]: time reset 4.572738 s
>Jan 28 22:47:56 linux ntpd[28795]: synchronisation lost
>We see these messages very often.
>Any help?
>- -- 
>Ruben Navarro Huedo
>eb5esx (arroba) eb5esx.ampr.org
>Version: GnuPG v1.2.1 (GNU/Linux)

More information about the questions mailing list