From owner-freebsd-current Mon Jul 15 09:40:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA22109 for current-outgoing; Mon, 15 Jul 1996 09:40:45 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.186.250]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA22104 for ; Mon, 15 Jul 1996 09:40:42 -0700 (PDT) Received: (from dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) id JAA00999; Mon, 15 Jul 1996 09:40:09 -0700 (PDT) Date: Mon, 15 Jul 1996 09:40:09 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: sthaug@nethelp.no cc: bde@zeta.org.au, current@freebsd.org Subject: Re: xntpd stepping clock backwards? (was: Re: NFSv3 fixes for review) In-Reply-To: <20426.837433714@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Jul 1996 sthaug@nethelp.no wrote: > > xntpd only does tiny adjustments which can't possibly make the clock > > go backwards. OTOH, ntpdate or ordinary `date' can set the clock back > > by years. > > Then why does my syslog show the following? It sure looks to me like xntpd > sometimes steps the clock backwards. This is on 2.2-960612-SNAP. I think you are misinterpeting the log entry. xtnpd works by adjusting the length of a 'tick' so the clock 'speeds up' or 'slows down' as necessary. This adjustment is called 'slew' and is inserted in very, very small increments. But time continues to move forward, even if it means slewing the ticks for quite a while. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major