From owner-freebsd-current Thu Jul 16 05:45:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04101 for freebsd-current-outgoing; Thu, 16 Jul 1998 05:45:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04095 for ; Thu, 16 Jul 1998 05:44:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id OAA02150; Thu, 16 Jul 1998 14:42:21 +0200 (CEST) To: jak@cetlink.net (John Kelly) cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Thu, 16 Jul 1998 12:37:44 GMT." <35adf2b5.224800464@mail.cetlink.net> Date: Thu, 16 Jul 1998 14:42:20 +0200 Message-ID: <2148.900592940@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35adf2b5.224800464@mail.cetlink.net>, John Kelly writes: >>>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 get it inside xntpd's capture range ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message