Re: Does Fedora mess up the clock for Windows?

Leon wrote:
"Lee Maschmeyer" <lee_maschmeyer@xxxxxxxxx> writes:

Hi all,

I have a dual boot system with FC5 and Windows XP. On FC5 I run ntpd
with the default config files. The drift file varies widely, from -0.4
or so to as much as -60 or 100 or more. Generally the longer Fedora is
up the smaller the number, though it's always negative.

But Windows is losing time hand over fist, maybe a couple minutes or
more in a 3-hour Windows session. I use an old program (AtomTime95) to
correct the Windows clock periodically but it doesn't do any permanent
good.

I had the same kind of thing happen with Fedora 4. It went away when I
installed Fedora 5 until I activated ntpd.

According to /var/log/messages Fedora has to set the clock back about
a second or so every time I boot it, but nowhere near the gargantuan
misalignment of Windows.

Does anybody have any idea how to make these two guys live happily
together sharing the clock? Yes, Fedora does use local time - at
least, that's the way I installed it..

Thanks much,

--
Lee Maschmeyer
<lee_maschmeyer@xxxxxxxxx>

"Be kind to your fur-bearing friends,
For a skunk may be somebody's brother."
--Fred Allen

Set UTC=false.

,----
| Setting UTC or local time
|
| When Linux boots, one of the initialisation scripts will run the
| /sbin/hwclock program to copy the current hardware clock time to the
| system clock. hwclock will assume the hardware clock is set to local
| time unless it is run with the --utc switch. Rather than editing the
| startup script, under Red Hat Linux you should edit the
| /etc/sysconfig/clock file and change the ``UTC'' line to either
| ``UTC=true'' or ``UTC=false'' as appropriate.
`----

You will have to double check, but running "hwclock --utc --systohc"
makes this change systems I have worked with. Running
"hwclock --localtime --systohc" will set it to local time.

With both Windows and Linux on the same machine, you probably should
have the hardware clock set to local time. Because the system time
is written back to the hardware clock when FC shuts down, you can
run into problem if it is not set correctly. If Linux expects UTC
and Windows expects local time, both end up doing large corrections
when they boot. You can end up with running corrections that are
based on an incorrect drift rate because you are trying to adjust to
the time zone difference every time you change the OS. You also run
into this problem when you change the hardware clock from local time
to UTC on a running system.

Mikkel
--

Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Internet time on computer
    ... boot OSX and Windows - OSX expects the internal BIOS clock to be GMT, Windows wants it to be local time, so the 2 operating systems fight w. ... Operating systems store and retrieve the time in the hardware clock located on your motherboard so that it can keep track of the time even when the system does not have power. ... Most operating systems store the time on the hardware clock as UTC by default, though some systems store the time on the hardware clock as the 'local' time. ...
    (alt.horology)
  • Re: [opensuse] opensuse 11.0 x64 time messed up with dual boot
    ... Basically my opensuse 11.0 is set to sync date/time with UTC and that works ... this is a dual boot machine (sorry VM windows is not fast ... Windows consider that hardware clock is set ...
    (SuSE)
  • Re: Time difference between Win98 and Fedora
    ... Since Windows will set the hardware clock to local time, ... > Now that Linux and Windows both expect the hardware clock to represent ... When you next boot into Windows, it will realize that it's the ...
    (Fedora)
  • Re: Date/Time setting
    ... Both Windows and Linux use UTC for timestamps. ... difference is, in Windows you set the hardware clock to your local time, ...
    (Fedora)
  • Re: Windows timekeeping
    ... So Windows could choose any timezone for the hardware clock, ... But I do believe that Windows systems still use local time, ... The system clock is a software/hardware construct with the software part belonging to Windows. ...
    (comp.protocols.time.ntp)