From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 19:50:37 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 B9F9616A4CE for ; Thu, 30 Dec 2004 19:50:37 +0000 (GMT) Received: from flyingjoke.org (soggy88.drizzle.com [216.162.199.88]) by mx1.FreeBSD.org (Postfix) with SMTP id 14F2F43D45 for ; Thu, 30 Dec 2004 19:50:37 +0000 (GMT) (envelope-from dtalk-ml@prairienet.org) Received: (qmail 85251 invoked from network); 30 Dec 2004 19:50:41 -0000 Received: from atlantis.flyingjoke.org (192.168.1.8) by atlantis.flyingjoke.org with SMTP; 30 Dec 2004 19:50:41 -0000 Date: Thu, 30 Dec 2004 11:50:23 -0800 (PST) From: dtalk-ml@prairienet.org X-X-Sender: dtalk@atlantis.flyingjoke.org To: Federico Galvez-Durand Besnard In-Reply-To: <41D458DF.3020706@bluewin.ch> Message-ID: <20041230113814.L17743@atlantis.flyingjoke.org> References: <41D43A7A.2000500@bluewin.ch> <20041230110953.T17743@atlantis.flyingjoke.org> <41D458DF.3020706@bluewin.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-stable@freebsd.org Subject: Re: clock running fast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dtalk-ml@prairienet.org 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 19:50:37 -0000 -----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-----