From owner-freebsd-hackers Tue Apr 11 1: 3:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maxim.gba.oz.au (gba.tmx.com.au [203.9.155.249]) by hub.freebsd.org (Postfix) with SMTP id 62E8637B948 for ; Tue, 11 Apr 2000 01:03:53 -0700 (PDT) (envelope-from gjb-freebsd@gba.oz.au) Received: (qmail 7555 invoked by uid 1001); 11 Apr 2000 12:02:29 +1000 X-Posted-By: GBA-Post 2.02.01 12-Dec-1999 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Tue, 11 Apr 2000 12:02:28 +1000 From: Greg Black To: FreeBSD-hackers@FreeBSD.ORG Subject: Kernel adjustment for clock drift Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been away from the FreeBSD lists for ages and am looking for an update on clock drift management under FreeBSD-3.4R. I asked this on -questions, but got no answers. Perhaps somebody here knows the answer. I have a machine that drifts about 7 seconds a day and I'd like to tweak something in the kernel to keep it closer to the truth. The clock gets corrected once a day by ntpdate, but I'd like to avoid such big adjustments. In the past I used a sysctl under BSDI's BSD/OS to adjust the value of `tick', but the whole kern.clockrate struct is marked as not changeable under FreeBSD. If anybody can tell me which FM has the answer (or even the actual answer), I'd be grateful. If your answer includes terms such as {,x}ntpd, then please don't bother, because that's not the answer (or even an answer) to this particular question. Please copy any replies to me as my subscription to the list is going off with this message and won't be completed for some time. -- Greg Black -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message