* Sean Cody <[EMAIL PROTECTED]> [2007-12-11 00:13]: > I've seen this happen too but ended up just shutting off ntpd entirely and > croned an rdate in it's place.
which is a very bad solution > In my case the clock goes WAAAAAAY out and even when I fix it it flys way > out on the next NTP interval. > Even if I restart NTPD the damned thing flies way out again a while later. > Snippet from /var/log/daemon: > > daemon:Nov 25 07:48:18 mail ntpd[1183]: adjusting local clock by > 59320.679282s [..] > daemon:Nov 25 10:13:02 mail ntpd[1183]: adjusting local clock by > 59107.913735s you log snippet actually shows ntpd/adjtime coping fine, the offset is getting smaller. you probably want to look into -s to compensate for the gigantic initial offset. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam
