From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1F8UzH-0000Y2-Ms for garchives@archives.gentoo.org; Mon, 13 Feb 2006 04:06:56 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1D45wJr005714; Mon, 13 Feb 2006 04:05:58 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1D41Qdv000445 for ; Mon, 13 Feb 2006 04:01:27 GMT Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by smtp.gentoo.org with esmtp (Exim 4.54) id 1F8Uty-0004uo-9g for gentoo-user@lists.gentoo.org; Mon, 13 Feb 2006 04:01:26 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1F8Uto-00016G-7S for gentoo-user@gentoo.org; Mon, 13 Feb 2006 05:01:16 +0100 Received: from adsl-68-78-151-55.dsl.emhril.ameritech.net ([68.78.151.55]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Feb 2006 05:01:16 +0100 Received: from reader by adsl-68-78-151-55.dsl.emhril.ameritech.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Feb 2006 05:01:16 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Harry Putnam Subject: [gentoo-user] Re: System Clock Problems Date: Sun, 12 Feb 2006 22:01:07 -0600 Organization: Still searching... Message-ID: <87d5hrkiv0.fsf@newsguy.com> References: <43EF962C.6030507@mykitchentable.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: adsl-68-78-151-55.dsl.emhril.ameritech.net User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:0cCzsxpZn51Poo/Y1RDPjlY58fw= Sender: news X-Archives-Salt: 4577381e-74d7-4ec0-bd3f-468dc0862f61 X-Archives-Hash: b667b241b02085068d3ff69bea17a9c3 Drew Tomlinson writes: > The time server is a FreeBSD 6.0 box on my network. My other FreeBSD > box and two Windows boxes get time from it just fine. Even the Gentoo > box will set its clock with "ntpd -gq". I am currently using this > brute force method via a cron job as a temporary workaround. > > Any ideas on what might have caused this recent change in behavior? It might be that the clock got off by more than ntp is willing to adjust. As I recall there is a threshold above which ntp will not go. Hopefully someone more knowledgable might confirm that. To cure that sort of problem here I run ntp-client at boot. It sets the time by any amount I think. So time gets set right on boot then ntp will keep it in good order. Next boot up ntp-client comes in ahead of ntp and sets the clock before ntp gets to it, so the too-large discrepancy never occurs. I seem to recall that the too-large discrepancy is not really that large. I remember thinking it seemed kind of small to be a problem. -- gentoo-user@gentoo.org mailing list