From owner-freebsd-doc@FreeBSD.ORG Thu Aug 12 13:38:45 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5C8616A4CE for ; Thu, 12 Aug 2004 13:38:45 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA19E43D46 for ; Thu, 12 Aug 2004 13:38:45 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id E557969A71 for ; Thu, 12 Aug 2004 09:38:44 -0400 (EDT) Date: Thu, 12 Aug 2004 09:38:43 -0400 From: Bill Moran To: doc@freebsd.org Message-Id: <20040812093843.30d57ad7.wmoran@potentialtech.com> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: FAQ entry on calcru could use updated X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 13:38:46 -0000 This FAQ entry is woefully out of date: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE The sysctl referenced doesn't even exist in newer versions of FreeBSD. I was going to write up a patch, when I found out that this entry: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#LAPTOP-CLOCK-SKEW actually contains the fix that I've used whenever I get the calcru problem on 5.x. I would suggest eliminating the answer in the calcru entry and merging the two entries, as the solution is the same on 5.x However, I've never seen the problem on 4.x, so I don't know if the technique of setting kern.timecounter.method=1 workes or not. Comments? Suggestions? -- Bill Moran Potential Technologies http://www.potentialtech.com