On 31Mar2008 16:21, Konstantin Svist <fry.kun(a)gmail.com> wrote:
Is there a good ["Fedora"] way to keep time synchronized on
I've checked around and ntpd seems to be a bad idea because it counts
CPU cycles - but modern CPUs switch frequencies all the time to save
power. Some tutorials say this causes NTP to not work properly.
Ntpd is the normal way. Why not try it out?
Ntpd (and any ntp daemon in general) does watch "drift", to keep an idea
of the discrepancy between your system clock and a correct clock, and
uses it the schedule time checks and general correction.
I do not have much knowledge about how CPU speed changes affect ntpd but I
would have thought: not much! The OS is supposed to keep "correct" time
(subject to drift) across these changes and no normal UNIX program counts CPU
cycles - in a multitaksing OS there's no guarentee of how much CPU your
getting anyway and on a modern CPU "cycles" are a loose and dodgy idea
anyway. Ntpd _should_ be looking at the system clock periodically, not
counting CPU cycles.
I suspect you will find ntpd works pretty well.
Cameron Simpson <cs(a)zip.com.au> DoD#743
There are two excuses for poor proof-reading. The first is incompetence, for
which the author should be killfiled. The second is indifference, for which
the author should be killed. - Dan Hillman <dcah100(a)cus.cam.ac.uk>