From owner-freebsd-current@FreeBSD.ORG Mon Jun 20 22:57:33 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA4E216A41C for ; Mon, 20 Jun 2005 22:57:33 +0000 (GMT) (envelope-from Chris@LainOS.org) Received: from mail.neovanglist.net (blackacid.neovanglist.net [69.16.150.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C909C43D1F for ; Mon, 20 Jun 2005 22:57:33 +0000 (GMT) (envelope-from Chris@LainOS.org) Received: from localhost (localhost.neovanglist.net [127.0.0.1]) by mail.neovanglist.net (Postfix) with ESMTP id B85606D43C for ; Mon, 20 Jun 2005 22:48:56 -0700 (MST) Received: from mail.neovanglist.net ([127.0.0.1]) by localhost (blackacid.neovanglist.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34821-07 for ; Mon, 20 Jun 2005 22:48:44 -0700 (MST) Received: from [10.0.0.3] (port2030.ds1-vbr.adsl.cybercity.dk [212.242.246.211]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.neovanglist.net (Postfix) with ESMTP id D505E6D438 for ; Mon, 20 Jun 2005 22:48:43 -0700 (MST) From: Chris Gilbert To: freebsd-current@freebsd.org Date: Tue, 21 Jun 2005 00:53:34 +0200 User-Agent: KMail/1.8 References: <20050617180321.GA1131@tarc.po.cs.msu.su> <42B5D82E.2090509@pop.agri.ch> <20050620130609.GA917@tarc.po.cs.msu.su> In-Reply-To: <20050620130609.GA917@tarc.po.cs.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506210053.34204.Chris@LainOS.org> X-Virus-Scanned: amavisd-new at neovanglist.net Subject: Timekeeping gone whack in 6-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Chris@LainOS.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2005 22:57:34 -0000 I've noticed since updating my machine from 5.3 to 6-CURRENT that the timekeeping on the system goes out of sync very quickly. After about a day, the clock is out of sync up to 12 hours! This is strange as on 5.3/5.4 the timekeeping on my machine was much more reasonable (+/- ~1 second a day) Is there something with 6-CURRENT that needs to be configured to keep this from going nuts? If any other diagnostic information is needed please let me know! -- Thanks, Chris (Lance) Gilbert Ph: +45 3373 2931 (UTC +0100)