On Mon, 2012-06-04 at 10:28 -0600, Greg Woods wrote:
> I have a fresh install of F17 that has some confusion about its
> timezone. The date displays as MDT (which is correct), but every time I
> boot the machine, it displays six hours ahead. Not coincidentally I'm
> sure, that is the offset betwee
On Mon, 2012-06-04 at 10:28 -0600, Greg Woods wrote:
> until the next reboot, at which point it's off by six hours again.
Tacky to answer myself, but I figured it out. I needed to run:
# hwclock --systohc
...to get the hardware clock updated. ntpdate only updates the system
clock.
--Greg
--
I have a fresh install of F17 that has some confusion about its
timezone. The date displays as MDT (which is correct), but every time I
boot the machine, it displays six hours ahead. Not coincidentally I'm
sure, that is the offset between MDT and GMT, so what I'm seeing is
correct GMT time but disp
