From owner-freebsd-questions@FreeBSD.ORG Wed May 4 21:06:00 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 361A816A4CE for ; Wed, 4 May 2005 21:06:00 +0000 (GMT) Received: from tomts16-srv.bellnexxia.net (tomts16.bellnexxia.net [209.226.175.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 276B743D6E for ; Wed, 4 May 2005 21:05:59 +0000 (GMT) (envelope-from james.cook@utoronto.ca) Received: from angel.falsifian.afraid.org ([67.70.139.43]) by tomts16-srv.bellnexxia.netSMTP <20050504210519.SVMH27508.tomts16-srv.bellnexxia.net@angel.falsifian.afraid.org>; Wed, 4 May 2005 17:05:19 -0400 Received: by angel.falsifian.afraid.org (sSMTP sendmail emulation); Wed, 4 May 2005 17:05:19 -0400 Date: Wed, 4 May 2005 17:05:19 -0400 From: James Alexander Cook To: "W. D." Message-ID: <20050504210519.GA51317@angel.falsifian.afraid.org> References: <42792740.3040501@houston.rr.com> <5.1.0.14.2.20050504154906.4311e370@209.152.117.178> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.2.20050504154906.4311e370@209.152.117.178> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org cc: Ryan Winograd Subject: Re: Clock running fast 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: Wed, 04 May 2005 21:06:00 -0000 On Wed, May 04, 2005 at 03:51:05PM -0500, W. D. wrote: > At 14:49 5/4/2005, Ryan Winograd, wrote: > >Hi all, > >I recently noticed that the system clock on a machine i recently set up > >is running very quickly, about 2x realtime by my measuring. What can i > >do to solve/investigate this problem? What information would be helpful? > > http://www.Google.com/search?q=install+ntp+on+FreeBSD I might be wrong here, but doesn't NTP only make occasional adjustments to the system clock? If your clock runs twice as fast as normal, it would jump to the correct time every time ntpd corrected it, but in between automatic adjustments, the time would become wildly innacurate. Also, wouldn't a problem like this make your system try to play movies at twice the frame rate, and things like that? NTP is worth a try, but I doubt if it will fix things like that. A google search for "fast clock" seemed to turn up a few results about this problem on mailing lists; I haven't looked into them further. - James Cook james.cook@utoronto.ca