mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Benoît Dejean" <TazForEver@free.fr>
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 16:25:48 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0405251619520.954@chaos> (raw)
In-Reply-To: <1085514395.11860.8.camel@athlon>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=UTF-8, Size: 817 bytes --]

On Tue, 25 May 2004, [ISO-8859-1] Benoît 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.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-05-25 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 17:39 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 [this message]
2004-05-25 20:34     ` Michael Buesch
2004-05-25 20:43     ` Benoît Dejean
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=Pine.LNX.4.53.0405251619520.954@chaos \
    --to=root@chaos.analogic.com \
    --cc=TazForEver@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbuesch@freenet.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®