From owner-freebsd-current Thu Oct 8 12:25:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28998 for freebsd-current-outgoing; Thu, 8 Oct 1998 12:25:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28981 for ; Thu, 8 Oct 1998 12:25:35 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id MAA23658; Thu, 8 Oct 1998 12:20:58 -0700 (PDT) (envelope-from jdp) Message-Id: <199810081920.MAA23658@austin.polstra.com> To: phk@critter.freebsd.dk Subject: Re: Is tickadj still required in -CURRENT ? In-Reply-To: <6169.907867530@critter.freebsd.dk> References: <6169.907867530@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 08 Oct 1998 12:20:58 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >The original question was "can tickadj be removed". You answered no. > > Sorry, misunderstanding there, yes I think it can be removed. It is still useful on 486 machines using the "-t nnnn" option to correct for badly inaccurate clocks. I don't know of a replacement for that. Even when running xntpd, this usage of tickadj keeps the /etc/ntp.drift value within the range claimed to be robustly compensated by xntpd. In any case, given that a code freeze is in effect, it shouldn't be removed before 3.0 is released. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message