Re: Does Fedora mess up the clock for Windows?

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
--
That's what I like about this list. I'm always learning. In the
meantime I agree with the subsequent post to yours that at bootup that
would be synched properly and immediately. So unless an application
after initial bootup went and changed the clock time to another time
zone which would result in the behaviour you noted from ntpd that
shouldn't happen. And if that is happening, then the earlier point I
found when Googling this is that it could be caused by an application
you installed messing with the clock.

Jacques B.

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

Relevant Pages

  • Re: clock problem
    ... This is a rather interesting misfeature of ntpd. ... the local clock can take a long time to converge ... frequency error of the system clock that ntpd can tolerate. ... : well supported on FreeBSD. ...
    (freebsd-stable)
  • Re: iburst
    ... Just a normal user trying to keep a somewhat accurate clock. ... When I finally got that worked out, my boot time went from about 1 minute to many minutes. ... I discovered that ntpd was the culprit. ... It takes ntpd several minutes to synch during boot. ...
    (comp.protocols.time.ntp)
  • Re: Clock drift problems
    ... the real-time clock has gotten 7 hours slow. ... I can understand that, but things like NTP ... Maximum drift rate for ntpd is 500ppm or something tiny like that. ... on x86 ATX motherboard linux boxes that are doing heavy I/O ...
    (comp.os.linux.misc)
  • Re: Reference Clock / shared memory driver
    ... entry creates a shared memory segment on startup with a defined shared ... I use a system clock time from another application via a 1553 bus from ... The problem is do NOT see my system clock being updated after the ntpd ... on the client machine i call ntpdate BEFORE i start the ntpd. ...
    (comp.protocols.time.ntp)
  • Re: Can a clock drift be too big for ntpd?
    ... 'burst' is an 8x multiplier; it causes ntpd to send a burst of 8 packets ... the kernel clock and the hardware clock. ...
    (comp.protocols.time.ntp)