From owner-freebsd-questions@FreeBSD.ORG Mon Jan 17 20:47:16 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE19E16A4CE for ; Mon, 17 Jan 2005 20:47:16 +0000 (GMT) Received: from dexter.starfire.mn.org (starfire.skypoint.net [66.93.17.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18F3D43D46 for ; Mon, 17 Jan 2005 20:47:16 +0000 (GMT) (envelope-from john@dexter.starfire.mn.org) Received: (from john@localhost) by dexter.starfire.mn.org (8.11.3/8.11.3) id j0HKlFw29256 for freebsd-questions@freebsd.org; Mon, 17 Jan 2005 14:47:15 -0600 (CST) (envelope-from john) Date: Mon, 17 Jan 2005 14:47:15 -0600 From: John To: freebsd-questions@freebsd.org Message-ID: <20050117144715.A29157@starfire.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: Kernel time-keeping adjustments - how to tune? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 20:47:17 -0000 OK - on my FreeBSD 5.3-STABLE system, as I have documented (cf: message thread Re: ntpd problems since upgrading to 5.3), ntpd won't run, even with an identical configuation to the 5.2.1 system next to it. Furthermore, when I run adjkerntz -a, it totally whacks the system's ability to keep time - it races forward at quite a high rate. ntpdate runs, and sets the time correctly. At one point, something managed to get the timekeeping parameters pretty near normal - less than a second of drift per hour (much better than the 40% rate it is now - it gains about 24 seconds PER MINUTE). Then I ran adjkerntz -a again, just to see if it really was the culprit. It does seem that it is adjkerntz that is causing (or triggering) the problem, but now I can't get the system back to a decent time-keeping rate. Whatever it was I stumbled across before, I'm not finding it again now. Now, it doesn't appear that adjkerntz itself has changed in YEARS, so it must be some change in the system call operation, parameters, or data structures that is causing this. So - since I don't seem to be able to stumble across what I did right before to get the timekeeping somewhat near normal, I am wondering if there's a manual way to reach them. -- John Lind john@starfire.MN.ORG