From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 20:58:54 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 328DB16A4CE for ; Thu, 30 Dec 2004 20:58:54 +0000 (GMT) Received: from mail15.bluewin.ch (mail15.bluewin.ch [195.186.18.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7D5D43D31 for ; Thu, 30 Dec 2004 20:58:53 +0000 (GMT) (envelope-from Federico.Besnard@bluewin.ch) Received: from [192.168.1.33] (62.203.145.231) by mail15.bluewin.ch (Bluewin AG 7.0.035) id 41CEF01C00040BBC; Thu, 30 Dec 2004 20:58:51 +0000 Message-ID: <41D46C0B.6050803@bluewin.ch> Date: Thu, 30 Dec 2004 21:58:51 +0100 From: Federico Galvez-Durand Besnard User-Agent: Mozilla Thunderbird 1.0 (X11/20041209) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dtalk-ml@prairienet.org References: <41D43A7A.2000500@bluewin.ch> <20041230110953.T17743@atlantis.flyingjoke.org> <41D458DF.3020706@bluewin.ch> <20041230113814.L17743@atlantis.flyingjoke.org> In-Reply-To: <20041230113814.L17743@atlantis.flyingjoke.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: clock running fast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 20:58:54 -0000 Hmmm, are you using the same localtime in all machines? I remember having the same problem several years ago, in 3.x, with a server. The clock kept walking. Hardware was OK. It came back to normal after setting localtime correctly. Remember, if you are in Pacific Time you are GMT+8 (some people wrongly uses GMT-8), it means you have to add 8h to your localtime in order to get GMT. Your NTPD will never be stable with a wrong localtime setting. Fico// dtalk-ml@prairienet.org wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Federico Galvez-Durand Besnard wrote: > >> Set /etc/localtime to your correct timezone before doing anything in >> your machine. Remove /var/db/ntpd.drift before you reboot or restart >> your ntpd. > > > [ rc.conf and ntp.conf snipped ] > > Thank you for the suggestions. Unfortunately, I've been through all > that, including the rude values of minpoll and maxpoll, using multiple > servers, and starting with a fresh drift file. I'm pretty sure ntpd > isn't the problem. In addition, the hardware clock itself appears to > be plenty accurate, as it is always correct within a second or two > when I check it directly in BIOS ... and two other 5.3-STABLE hosts on > the same network, with the same ntpd configuration, but on different > hardware, do not have this problem, which began when I updated > (reinstalled) to 5.3-STABLE from 5.2. > > - -- David Talkington > dtalk-ml@prairienet.org > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.6 (FreeBSD) > > iD8DBQFB1FwQ5FKhdwBLj4sRArSqAJwK8MAvUfB69ixoHNzu8700Pvd52QCgl0dD > 07gb7ipg0ENIcUN/PPHhXpw= > =Lv+T > -----END PGP SIGNATURE----- >