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 1F8hot-0007m3-Hg for garchives@archives.gentoo.org; Mon, 13 Feb 2006 17:49:03 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1DHm1jT016675; Mon, 13 Feb 2006 17:48:01 GMT Received: from relay03.roc.ny.frontiernet.net (relay03.roc.ny.frontiernet.net [66.133.182.166]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1DHhdo6000795 for ; Mon, 13 Feb 2006 17:43:40 GMT Received: from blacklamb.mykitchentable.net (70-97-209-135.dsl2.elk.ca.frontiernet.net [70.97.209.135]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id 7A0583585AD for ; Mon, 13 Feb 2006 17:43:38 +0000 (UTC) Received: from [192.168.1.30] (unknown [192.168.1.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTP id 7C4B11648AE for ; Mon, 13 Feb 2006 09:43:37 -0800 (PST) Message-ID: <43F0C548.7050306@mykitchentable.net> Date: Mon, 13 Feb 2006 09:43:36 -0800 From: Drew Tomlinson User-Agent: Thunderbird 1.5 (Windows/20051201) 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: System Clock Problems References: <43EF962C.6030507@mykitchentable.net> <87d5hrkiv0.fsf@newsguy.com> In-Reply-To: <87d5hrkiv0.fsf@newsguy.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-2.3.2 (20050629) at filter05.roc.ny.frontiernet.net X-Archives-Salt: 71e862e9-8774-496d-859d-a98ab337e8fa X-Archives-Hash: ae85b510f8c3f6074589b6fa83189374 On 2/12/2006 8:01 PM Harry Putnam wrote: > 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. > Thanks for your reply. If I understand correctly, using the '-g' option will allow a one time clock adjustment of any size. > 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 have used both 'ntpupdate' (the utility used by ntp-client) and 'ntpd -gq' (ntpd's way to mimic the behavior of ntpupdate) with successful results. However I still can not seem to get ntpd to sync when run in daemon mode. > 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. > 1000 seconds according to my understanding of the man page. Anyway, I really appreciate your thoughts. Because this box runs MythTV, time is *VERY* important. Imagine my surprise when I went to watch the first day of the Olympics on to find out that my recordings were off by over an hour and half. :) Thanks, Drew -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, & More! http://www.alchemistswarehouse.com -- gentoo-user@gentoo.org mailing list