On Wed, 26 Jun 2002, Tom Pollerman wrote: > See 'man hwclock.' > " hwclock --systohc > Set the Hardware Clock to the current System Time." > > If your hardware clock was correct, and your system clock was 4 > hours off, your hardware clock is now also 4 hours off. > Additionally, hwclock --set or hwclock --systohc makes note of the > time difference between the hardware and system clock in the file > /etc/adjtime. The system tries to compensate for the difference using > this file; ie., assumes a drift. > If you do hwclock --hctosys after setting your CMOS clock to the > correct time, it should get things straight. To keep it from changing > make sure that /etc/adjtime shows zeros. Here's mine: > > 0.000.0 > 0
ahhhhhh ... now it's starting to make a bit more sense. perhaps, when i was goofing around earlier and playing with the --utc option, i introduced a 4-hour drift into that file, and it's been playing havoc with me ever since. i deleted that file, reset the hw clock based on the system clock, and that file now reads: 0.000000 1025116160 0.000000 1025116160 LOCAL which doesn't quite match your format. i'll check the man page to see what these values mean, but that seems to have done the trick. thanks. rday _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
