On Tue, 2012-01-10 at 13:02 -0600, Dale wrote: > Florian Philipp wrote: > > Besides, ntpd does not correct such large differences. It is not > > designed to do this, especially on a running system. Activate > > /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it > > in sync afterwards. You can start ntp-client on a running system but > > it might lead to funny errors or crashes of applications. Better add > > it to runlevel default and restart. Regards, Florian Philipp > > Two things. One, you need to set the clock manually since it is soooo > far off. I would do this: > > ntpdate -b -u pool.ntp.org > > then start ntpd. Second thing, if you are dual booting with windows, > you have to edit the config file to set it correctly: It is set in > /etc/conf.d/hwclock and it has a message about how to set it. I think > it is UTC. It tells you in the file tho. If it is not in yours, let me > know and I'll post it. > > Dale > > :-) :-) > Thanks.
ntpdate -b -u pool.ntp.org synchronised my clock. My system is not tainted by Windoze, so no problems there. I'm still a little concerned by the results of hwclock --debug hwclock from util-linux 2.20.1 hwclock: Open of /dev/rtc failed: No such file or directory No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. Initially, the RTC options were not enabled in my kernel, but even after setting these, I'm still getting this error. I'm adding all the device drivers as modules and trying again to see if I can remove this error. I suspect it is the root cause of my ntp issues. Jeff
