On Wed, 17 Aug 2005, Joe Brandt wrote:
> Levi Bard wrote:
>
> >>>Try running ntpd?
http://lists.suse.com/archive/suse-linux-e/2005-Feb/3719.html concurs.
> >>How would that slow down his system clock?
> >
> >It wouldn't slow down the actual clock speed, but it could fix the
> >visual symptoms (e.g. clock shows wrong time), while not forcing him
> >to deal with the -noapic breakage.
> >
> Sounds logical. How often would he have to correct?
It depends how accurate it needs to be. If there's another nearby machine
to use (I mean, on the same LAN), what the heck -- once every few seconds.
I believe ntpd "learns" how much the system clock can be expected to be off,
and apply an appropriate clock slew between updates.
Also, if the hardware clock runs at the correct speed (or at least close to
it), consider doing something like
#! /bin/sh
while : ; do
hwclock --hctosys
sleep $SMALLNUM
done
and writing to the hardware clock just after ntp does its thing.
-- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? [TOFU := text oben, A: Top-posting. followup unten] Q: What is the most annoying thing on usenet? -- Daniel Jensen----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:13:48 EDT