From: "Benoît Dejean" <TazForEver@free.fr>
To: root@chaos.analogic.com
Cc: Michael Buesch <mbuesch@freenet.de>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: System clock running too fast
Date: Tue, 25 May 2004 22:43:38 +0200 [thread overview]
Message-ID: <1085517817.11860.17.camel@athlon> (raw)
In-Reply-To: <Pine.LNX.4.53.0405251619520.954@chaos>
Le mar, 25/05/2004 à 16:25 -0400, Richard B. Johnson a écrit :
> On Tue, 25 May 2004, [ISO-8859-1] Benot Dejean wrote:
>
> > Le mar, 25/05/2004 à 19:39 +0200, Michael Buesch a écrit :
> > > Hi,
> > >
> > > I've got the problem with my server, that the system-clock
> > > is running really fast. It's running over one second too
> > > fast in one hour (aproximately).
> >
> > you should adjust it with adjtimex (there's a debian package)
> >
>
> Ahahh.. Did you accidentally set CONFIG_MELAN in .config? That would
> do about 1 second fast per hour. If not, then do: echo "">/etc/adjtime
> (used to be you could delete it), now I think you
> need to truncate it. Sometimes this file gets corrupt and
> it takes many settings of stime to undue the corrupt-ness.
no
cat /etc/adjtime
-0.541692 1084270031 0.000000
1084270031
LOCAL
before, my /etc/adjtime was empty, i was loosing 4.36s / 24H
i sync my clock every 15days, and the difference is always < 0.1s (-0.04
average)
so i'm pretty happy with it
--
Benoît Dejean
JID: TazForEver@jabber.org
http://gdesklets.gnomedesktop.org
http://www.paulla.asso.fr
next prev parent reply other threads:[~2004-05-25 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 17:39 System clock running too fast Michael Buesch
2004-05-25 18:13 ` Petri Kaukasoina
2004-05-25 18:45 ` Felipe Alfaro Solana
2004-05-25 18:49 ` Michael Buesch
2004-05-25 19:13 ` Felipe Alfaro Solana
2004-05-25 19:46 ` Benoît Dejean
2004-05-25 20:25 ` Richard B. Johnson
2004-05-25 20:34 ` Michael Buesch
2004-05-25 20:43 ` Benoît Dejean [this message]
2004-05-25 20:50 ` john stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1085517817.11860.17.camel@athlon \
--to=tazforever@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.