From owner-freebsd-current Thu Jul 16 01:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10059 for freebsd-current-outgoing; Thu, 16 Jul 1998 01:40:12 -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 BAA10044 for ; Thu, 16 Jul 1998 01:40:09 -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 EAA17156; Thu, 16 Jul 1998 04:36:26 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Poul-Henning Kamp Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 08:38:25 GMT Message-ID: <35aeb750.209593961@mail.cetlink.net> References: <278.900573807@critter.freebsd.dk> In-Reply-To: <278.900573807@critter.freebsd.dk> 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 BAA10049 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 09:23:27 +0200, Poul-Henning Kamp 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 want to fiddle kern.timecounter.frequency (units: Hz) or >kern.timecounter.adjustment (Units: PPM/2^16) Judging from what Bruce said, it seems that kern.timecounter.frequency is derived from the machdep.*_freq variables, so it would be better to change them and let the kernel propagate the changes. And if the appropriate machdep.*_freq variable is set precisely, is there any need for kern.timecounter.adjustment? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message