From owner-freebsd-questions@FreeBSD.ORG Tue May 27 07:26:56 2003 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 EE74437B401 for ; Tue, 27 May 2003 07:26:56 -0700 (PDT) Received: from empire.explosive.mail.net (empire.explosive.mail.net [205.205.25.120]) by mx1.FreeBSD.org (Postfix) with SMTP id B648A43FA3 for ; Tue, 27 May 2003 07:26:55 -0700 (PDT) (envelope-from mykroft@explosive.mail.net) Received: (qmail 1415 invoked from network); 27 May 2003 14:26:19 -0000 Received: from ticking.explosive.mail.net (HELO ticking) (205.205.25.116) by empire.explosive.mail.net with SMTP; 27 May 2003 14:26:19 -0000 Message-ID: <1f0101c3245c$1b1f67a0$7419cdcd@ticking> From: "Adam Maas" To: "Nan Wang" , References: Date: Tue, 27 May 2003 10:27:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Subject: Re: The clock is too fast in FreeBSD! 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: Tue, 27 May 2003 14:26:57 -0000 ----- Original Message ----- From: "Nan Wang" To: Sent: Tuesday, May 27, 2003 10:17 AM Subject: The clock is too fast in FreeBSD! > Hi! > The clock in FreeBSD is too fast! > I tried GENERIC kernel, the BSD clock is still too fast. > the problem is on 5.0 Release, 5.1 BETA1, and 5.1 BETA2. > I have not yet tried 4.x. > I'm using PII 366Mhz Acer notebook w/ 192mb RAM ALi Chipset > but there is no problem on Win98 and Linux(Redhat 8) > > I guess, in a Windows system, the timing function read time > from CMOS(Hardware Clock), where as FreeBSD just add itself > which is too dangerous for a server. > > Hope the problem will be solved in future. > good luck. > > > Eric. The Hardware clock isn't trustworthy either. for a server, you should be running ntpd and syncing with an atomic clock anyways. Adam