From owner-freebsd-current Thu Jul 16 05:38:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03400 for freebsd-current-outgoing; Thu, 16 Jul 1998 05:38:40 -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 FAA03391 for ; Thu, 16 Jul 1998 05:38:38 -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 IAA29977; Thu, 16 Jul 1998 08:34:54 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 12:37:44 GMT Message-ID: <35adf2b5.224800464@mail.cetlink.net> References: <1168.900581842@critter.freebsd.dk> In-Reply-To: <1168.900581842@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 FAA03394 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 11:37:22 +0200, Poul-Henning Kamp wrote: >>Argh! So should I change both kern.timecounter.frequency and the >>machine dependent variable? Will that work? > >This is why it is so much easier just to start xntpd and be done with it. > >They only time where you need to tweak any sysctl's is when the hardware >is outside the capture range (+/- 128 PPM ?) of xntpd. That's true for my hardware. >After I implemented timecounters, time keeping doesn't depend on tick, >and since the adjustment is for all practical purposes continuous, >there is no benefit of tweaking the sysctls. That sounds contradictory to the previous paragraph. So why tweak sysctls when it's outside the capture range of xntpd? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message