Date: Thu, 16 Jul 1998 13:04:48 GMT From: jak@cetlink.net (John Kelly) To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Message-ID: <35adf8c4.226351854@mail.cetlink.net> In-Reply-To: <2148.900592940@critter.freebsd.dk> References: <2148.900592940@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Jul 1998 14:42:20 +0200, Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: >>>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 ? First you say don't bother, then you say it's worthwhile. Since tweaking sysctls is sometimes needed to get the hardware within xntpd's capture range, then, even in the case where the hardware may be within the capture range, why not go ahead and tweak the sysctl to a more accurate value? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35adf8c4.226351854>