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.43) id 1E7Zt5-0003PI-5n for garchives@archives.gentoo.org; Tue, 23 Aug 2005 14:36:27 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7NEVtMJ008427; Tue, 23 Aug 2005 14:31:55 GMT Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7NEPJoZ011654 for ; Tue, 23 Aug 2005 14:25:19 GMT Received: by zproxy.gmail.com with SMTP id v1so921518nzb for ; Tue, 23 Aug 2005 07:26:12 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UxAZnj09Bdhq0D70kgr/AOSnh03buhuABChKD/SSJ6HA2Sp5w/nDigY060Q6OeLdGEwM8sDtg9QcQN8E/5rdzB7E59gdwUP6g3Cl6MatM6n80lgVI1DbLdSjEypZrk7BXiD9Il4T1Oy4Xya1X1LRN7Qx3syKO0YuE7gxJLPAEa8= Received: by 10.36.221.52 with SMTP id t52mr5181391nzg; Tue, 23 Aug 2005 07:26:11 -0700 (PDT) Received: by 10.36.34.4 with HTTP; Tue, 23 Aug 2005 07:26:11 -0700 (PDT) Message-ID: Date: Tue, 23 Aug 2005 11:26:11 -0300 From: Bruno Lustosa To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] ntp problem In-Reply-To: <2ab8d39a050823071990b8aad@mail.gmail.com> 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=ISO-8859-1 Content-Disposition: inline References: <430B23F6.9070706@badapple.net> <2ab8d39a050823071990b8aad@mail.gmail.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j7NEPJoZ011654 X-Archives-Salt: c7a76591-a402-47d9-8cbe-57b4a77848d4 X-Archives-Hash: 77ad467613369a631545ff27683ed4b4 On 8/23/05, krzaq wrote: > Hmmmm... > If you specify one timeserver, ntp cannot tell which clock is drifting > away (local > or remote). Ntpd trusts the local clock more than the remote one. > Large offsets cause ntpd to discard 192.168.7.1 as reliable timesource. > Try adding on this one machine more time servers and observe what will happen. I have another network of servers that are on a hosting company. I'll set up ntpd on one of those machines and let the internal machines get in sync with these 2 servers and see what happens. I guess I have lots of things to learn about ntp's internals. Thanks -- Bruno Lustosa, aka Lofofora | Email: bruno@lustosa.net Network Administrator/Web Programmer | ICQ: 1406477 Rio de Janeiro - Brazil | -- gentoo-user@gentoo.org mailing list