You are not logged in.
Pages: 1
My hwclock is correct. However, --systohc doesn't work. I also tried ntp and openntpd and they don't help any either.
Has anyone had a super-stubborn system clock?
I have tried UTC, localtime and the whole shebang. I can make the system clock change if I alter my location but I don't want to spoof my location just to fix my time. My location is set correctly but my system clock is about 14 hours in the future.
Last edited by Google (2011-08-12 01:17:14)
Offline
Please post the output of 'hwclock --debug' (run as root).
Offline
hwclock from util-linux 2.19.1
Using /dev interface to clock.
Last drift adjustment done at 1313128033 seconds after 1969
Last calibration done at 1313128033 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/08/12 15:07:28
Hw clock time : 2011/08/12 15:07:28 = 1313129248 seconds since 1969
Fri 12 Aug 2011 03:07:28 PM KST -0.063131 seconds
Offline
I suggest setting the hardwareclock to UTC. If you still have problems, set it to UTC both in /etc/rc.conf and in /var/lib/hwclock/adtime (third line sheald read "UTC"). Make sure your timezone is set correctly, and then you ntpd (not openntpd) to synchronize the time. You might need to pass ntpd the right option to force a timeset, in case the gap is to large.
Offline
Thanks--
Setting the hwclock to UTC and manually setting the clock-- and then running ntp did the trick.
Offline
Pages: 1