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 1E7Zgb-0003ZN-Sm for garchives@archives.gentoo.org; Tue, 23 Aug 2005 14:23:34 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7NELn6E017367; Tue, 23 Aug 2005 14:21:49 GMT Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7NEI8iM000333 for ; Tue, 23 Aug 2005 14:18:09 GMT Received: by zproxy.gmail.com with SMTP id x7so893424nzc for ; Tue, 23 Aug 2005 07:19:01 -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=DzTePSyBET/IUoFOJ6OCPv7diG+bc4v+n+RueeJAcxth5oED1CfwRUPedtmabwQJvfacYSK0bonXFRuVYuzaE7YiSYQ2wfEQG9F+N5xPsbIKSR/UKoyQDNvF76cY+/v1xvmZvUVvAavV5/eJ/kdwwkBhxbN4OUJeFisQ4LKaS3g= Received: by 10.37.2.57 with SMTP id e57mr3587599nzi; Tue, 23 Aug 2005 07:19:01 -0700 (PDT) Received: by 10.36.67.4 with HTTP; Tue, 23 Aug 2005 07:19:01 -0700 (PDT) Message-ID: <2ab8d39a050823071990b8aad@mail.gmail.com> Date: Tue, 23 Aug 2005 16:19:01 +0200 From: krzaq To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] ntp problem In-Reply-To: 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> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j7NEI8iM000333 X-Archives-Salt: 4672e3af-fcd3-4daa-925c-c61b3707b82e X-Archives-Hash: 6787c194d032433a5929d47e43b7d09d On 8/23/05, Bruno Lustosa wrote: > On 8/23/05, kashani wrote: > > That offset looks rather large. NTP really wants to make constant small > > changes, not a single huge change. This is why the ntpd setup allows for > > an immediate sync via ntpdate before starting the daemon. To fix this > > I'd shut down ntpd, run ntpdate 192.168.7.1, and then start ntpd again. > > That's what I did yesterday before leaving work. It synced with > ntpdate, and I left ntpd running. Today, the offset was like that. > That's what I don't understand. 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. -- Regards Karol Krzak -- gentoo-user@gentoo.org mailing list