From owner-freebsd-current  Thu Jul 16 07:47:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA19806
          for freebsd-current-outgoing; Thu, 16 Jul 1998 07:47:20 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from localhost.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19799
          for <current@freebsd.org>; Thu, 16 Jul 1998 07:47:18 -0700 (PDT)
          (envelope-from mi@rtfm.ziplink.net)
Received: from rtfm.ziplink.net (mi@rtfm [199.232.255.52])
	by localhost.ziplink.net (8.8.8/8.8.7) with ESMTP id OAA03900
	for <current@freebsd.org>; Thu, 16 Jul 1998 14:47:06 GMT
	(envelope-from mi@rtfm.ziplink.net)
Received: (from mi@localhost)
	by rtfm.ziplink.net (8.8.8/8.8.5) id KAA06046
	for current@freebsd.org; Thu, 16 Jul 1998 10:47:06 -0400 (EDT)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199807161447.KAA06046@rtfm.ziplink.net>
Subject: Re: tickadj -t not changing tick
In-Reply-To: <35aeb750.209593961@mail.cetlink.net> from "John Kelly" at "Jul 16, 98 08:38:25 am"
To: current@FreeBSD.ORG
Date: Thu, 16 Jul 1998 10:47:06 -0400 (EDT)
X-Face: 
	%UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
		 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
		 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Kelly once stated:

=On Thu, 16 Jul 1998 09:23:27 +0200, Poul-Henning Kamp
=<phk@critter.freebsd.dk> wrote:

=>The real way is to run ntpd, if you don't have a permanent connection,
=>consider looking into "burstmode" in the new xntpd4...

=According to John Polstra in an archived message about tickadj, his
="real way" is to adjust the undisciplined clock before running xntpd,
=formerly with tickadj, but now via sysctl as Bruce suggested.  I like
=the idea of getting the kernel synchronized with the hardware before
=trying to run xntpd.
[...]

You, people, are just kidding, right? There is no way this nonsense
is going to be required for longer then a week, until one wizard
or another commits a patch? My machine hare not only ran windoze
without time problems before it came to my hands, it also ran
FreeBSD-2.2 with clock running just peachy.

	-mi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message