From owner-freebsd-current Thu Jul 16 09:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01642 for freebsd-current-outgoing; Thu, 16 Jul 1998 09:11:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01636 for ; Thu, 16 Jul 1998 09:10:53 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id MAA20799; Thu, 16 Jul 1998 12:10:34 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 16:13:26 GMT Message-ID: <35ae253a.237736064@mail.cetlink.net> References: <199807161447.KAA06046@rtfm.ziplink.net> In-Reply-To: <199807161447.KAA06046@rtfm.ziplink.net> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA01637 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 10:47:06 -0400 (EDT), Mikhail Teterin 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? Totally and deadly serious. >There is no way this nonsense is going to be required for longer then >a week, until one wizard or another commits a patch? Many wizards have committed many patches just to get us where we are today. >My machine hare not only ran windoze without time problems before it >came to my hands That speaks for itself. >it also ran FreeBSD-2.2 with clock running just peachy. Clock? You mean a little X app? Wheeeee! (Sorry, but one silly post deserves another) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message