Re: Bizarre Clock Problem

To: debian-user@lists.debian.org
Cc: keithmur@mindspring.com
Subject: Re: Bizarre Clock Problem
From: Matthew Tuck <matty@box.net.au>
Date: Tue, 17 Aug 1999 18:31:34 +0930
Message-id: <[🔎] 37B924EE.7A82D8A8@box.net.au>
References: <[🔎] 37B63899.AFB4BF91@box.net.au> <[🔎] 19990815020909.A588@owl.zoo> <[🔎] 37B6F739.3DBEC547@stic.net> <[🔎] 14263.13037.139829.616257@greycat.penguinpowered.com> <[🔎] 37B74FE3.75E0C001@stic.net> <[🔎] 37B83A46.8C311CD1@mindspring.com>

"Keith G. Murphy" wrote:

> It may actually be due to the *documented* behavior of adjtime.
> ...

This makes a lot of sense.  I vaguely remember something about this
happening when I found my clock out by months.

In this case, I imagine it would be a good idea to set a drift
threshhold wherein adjtime data is not recorded for large drifts due to
likely inaccuracies.

-- 
     Matthew Tuck - Software Developer & All-Round Nice Guy
             mailto:matty@box.net.au (ICQ #8125618)
       Check out the Ultra programming language project!
              http://www.box.net.au/~matty/ultra/

Reply to:

References:
- Bizarre Clock Problem
  - From: Matthew Tuck <matty@box.net.au>
- Re: Bizarre Clock Problem
  - From: Alexander Stavitsky <stalex@physlab.sci.ccny.cuny.edu>
- Re: Bizarre Clock Problem
  - From: John Carline <jtc@stic.net>
- Re: Bizarre Clock Problem
  - From: Judith Elaine Bush <bush@grey-cat.com>
- Re: Bizarre Clock Problem
  - From: John Carline <jtc@stic.net>
- Re: Bizarre Clock Problem
  - From: "Keith G. Murphy" <keithmur@mindspring.com>

Prev by Date: leafnode won't fetch
Next by Date: which pgp package?
Previous by thread: Re: Bizarre Clock Problem
Next by thread: Re: Bizarre Clock Problem
Index(es):
- Date
- Thread