Re: Does Fedora mess up the clock for Windows?

Jacques B. wrote:
With the way the clock drift is happening, it sounds like a time
zone setting problem. Both Linux and Windows XP will slowly adjust
the clock to match the NTP server. Now, if the time zone setting is
wrong, the system will gain/lose time as it runs, until it matches.
Running the AtomTime95 program under windows would probably make
things worse by fighting with the NTP program windows is already
running. Making sure that the time zone is the same under both
Windows and Linux, making sure it is the correct time zone, and not
using AtomTime95 should fix the problem.

Mikkel
--
I'm confused about this one. I don't see time zone settings being the
issue as that would cause the time to be off by an hour (or two, or
whatever depending on the time zone) not drift by a few minutes to
100+ minutes over the course of a few hours. And Windows or Linux
would not slowly adjust the clock to match NTP, it synchronizes with
it and changes it to match. What would be the reason for Windows or
Linux slowly changing the time to synch up with NTP? It's not a bad
suggestion to check and make sure that they have the same time zone
settings. But that would not account for clock "drifting".

Jacques B.

ntpd does not normally make one large change. Instead, it will
slowly change the clock over time. This is especially true if the
system clock is ahead of the correct time. Turning back the clock
can cause interesting problems for any program that uses system time
or timestamps. So what is done instead is that the clock is slowed
down instead, until the time matches. (I think it skips every nth
time tick.) On the other hand, if the difference is too large, ntpd
should exit with an error.

From man ntpd:
Under ordinarily conditions, ntpd adjusts the clock in small steps
so that the timescale is effectively continuous and without
discontinuities.


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: Need to implement a calendar clock with millisecond resolution, please help.
    ... clock, not a per-CPU counter, since those may not be or stay in sync. ... I'm confident Windows does provide such a capability, ... standard for this called NTP ... they provide this support for NTP free presumably in the hope that ...
    (comp.lang.c)
  • Re: NTP Synchronisation Problem
    ... >> You dont say which version of Windows or include any config files so its ... >> SNTP client to an NTP server. ... >> Time service doesn't take into account clock drift, clock reliability, ...
    (comp.unix.sco.misc)
  • Re: Clock Problem?
    ... If his system gains a sec per sec ntp can ... Maybe something added something faulty in /etc/adjtime. ... and I've asked him to see if Windows handles the time correctly. ... Unless there is a file that got corrupted by changing the clock by hand ...
    (alt.os.linux.suse)
  • Re: 8.2 pro & RAID
    ... > So does it look like I've fixed the clock problem this time? ... Is your time zone correctly ... set to CST? ... One way to avoid this (if you don't dual-boot to Windows) is to set ...
    (alt.os.linux.suse)
  • Re: Clock ALWAYS an hour behind on startup
    ... I didn't have that little box checked at the bottom for daylight saving ... > That -0700 indicates that you have not changed your time zone from the ... > Double-click the clock in the lower right corner of your Desktop. ... > Microsoft Windows MVP ...
    (microsoft.public.windowsxp.general)