A probably blindingly-obvious question, but its answer continues to escape me: I have two x86 boxes both running virtually identical versions of RedHat 9. Unfortunately, one of these machines is not successfully working with my backup system (Dantz Retrospect), while the other one works fine. I've narrowed it down to the following situation:
GoodMachine: hwclock --debug
hwclock from util-linux-2.11y
Using /dev/rtc interface to clock.
Last drift adjustment done at 1077909647 seconds after 1969
Last calibration done at 1077909647 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: 2004/03/01 19:51:14
Hw clock time : 2004/03/01 19:51:14 = 1078199474 seconds since 1969
Mon Mar 1 19:51:14 2004 -0.813675 seconds
BadMachine: hwclock --debug
hwclock from util-linux-2.11y
Using /dev/rtc interface to clock.
Last drift adjustment done at 1078199348 seconds after 1969
Last calibration done at 1078199348 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: 2004/03/01 19:50:48
Hw clock time : 2004/03/01 19:50:48 = 1078199448 seconds since 1969
Mon 01 Mar 2004 07:50:48 PM PST -0.295439 seconds
The difference, of course, is in the last lines of the output, which show that GoodMachine is in one situation, while BadMachine is in the other. I'm assuming that this is because of something I did to BadMachine at some time in the past, and that if I can get BadMachine's hardware clock into the same state as GoodMachine, my problems will go away. But, so far, I haven't found the magic incantation. Can anyone help with this? As I said, it's probably bleeding obvious, but I just haven't been able to find it.
It may be worth mentioning that I also have a Windows ME partition on this (somewhat dated) machine, so Windows has occasionally gotten its hands on the clock...
Thanks,
Jim
GoodMachine: hwclock --debug
hwclock from util-linux-2.11y
Using /dev/rtc interface to clock.
Last drift adjustment done at 1077909647 seconds after 1969
Last calibration done at 1077909647 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: 2004/03/01 19:51:14
Hw clock time : 2004/03/01 19:51:14 = 1078199474 seconds since 1969
Mon Mar 1 19:51:14 2004 -0.813675 seconds
BadMachine: hwclock --debug
hwclock from util-linux-2.11y
Using /dev/rtc interface to clock.
Last drift adjustment done at 1078199348 seconds after 1969
Last calibration done at 1078199348 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: 2004/03/01 19:50:48
Hw clock time : 2004/03/01 19:50:48 = 1078199448 seconds since 1969
Mon 01 Mar 2004 07:50:48 PM PST -0.295439 seconds
The difference, of course, is in the last lines of the output, which show that GoodMachine is in one situation, while BadMachine is in the other. I'm assuming that this is because of something I did to BadMachine at some time in the past, and that if I can get BadMachine's hardware clock into the same state as GoodMachine, my problems will go away. But, so far, I haven't found the magic incantation. Can anyone help with this? As I said, it's probably bleeding obvious, but I just haven't been able to find it.
It may be worth mentioning that I also have a Windows ME partition on this (somewhat dated) machine, so Windows has occasionally gotten its hands on the clock...
Thanks,
Jim
Facebook
Twitter