yes, think the worse I saw was about 10min/week. I suppose you could do
the rough adjust with adjtimex for the average, then ntp would only have to
take care of the fine adjustment. As for no rpm, it's extremely easy just
to pull it down, and build it. Most all programs are just 4 steps, "tar
-xzvf tarball", "./configure", "make", and "make
install". I've compiled
what seems like hundreds of programs with nary a hitch.
On 2/16/02 10:12 PM, "Ron McCall" <ronald.mccall(a)snet.net> wrote:
Have you heard about many other people that have had to use NTP to keep
decent time? This is the first machine I've ever encountered that has
had this problem.
I think you're right, NTP is pretty painless, especially since my net
connection is up all the time. It has made 38 corrections in just under
6 hours so far ranging from about 0.25 seconds to about 4.5 seconds
depending on the execution interval which has varied from about 4
minutes to about 31 minutes.
On Sat, Feb 16, 2002 at 09:48:30PM -0700, Dave Gomez wrote:
although 3 minutes a day seems extreme, I don't think it's way out
of the ordinary either. After reading the manual, they state that
adjtimex is more elegant, but I also think it would take a long time
to get it to be accurate though. What I mean is that you would have
to do a long time study to understand the amount of drift you have,
make an adjustment ( or an adjustment to the adjustment) and start
again, except with an even longer time period. Ntp is more expedient,
and at multiple times a day, with an open connection, no pain.