In article <[email protected]>, scar <[email protected]> wrote: >ntpd does not seem to be doing it's job. i have Ver. 4.2.6p5 installed >on 6.1.5 and after 51 days of uptime, the system clock is 5 minutes >behind and the offset just keeps increasing. ntpdate seems to work fine >when the system boots, but ntpd just isn't maintaining the time after boot. > >here is my ntpd.conf: http://pastebin.com/EbxzPBw7 > >i noticed /var/db/ntp.drift doesn't exist which sounds important to keep >the time maintained.... > ># ntpq -p > remote refid st t when poll reach delay offset >jitter >============================================================================== >+Maggie.Telcom.A 132.163.4.102 2 u 6 64 377 0.455 297275. >19.763 ># > >i used to have "restrict ntp.arizona.edu nomodify notrap" after the >server line at the end of the conf file but it sounds like those >settings prevent ntpd from working, so i removed it. but after >restarting ntpd, the offset reported by ntpq just keeps increasing
Did you run ntpdate first to sync the time? christos
