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 1FBzNx-00005O-8W for garchives@archives.gentoo.org; Wed, 22 Feb 2006 19:10:49 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1MJ9nwq018294; Wed, 22 Feb 2006 19:09:49 GMT Received: from ender.volumehost.net (adsl-69-154-123-202.dsl.fyvlar.swbell.net [69.154.123.202]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1MJ5u7e032705 for ; Wed, 22 Feb 2006 19:05:56 GMT Received: from localhost (localhost [127.0.0.1]) by ender.volumehost.net (Postfix) with ESMTP id 92082CC59 for ; Wed, 22 Feb 2006 19:05:55 +0000 (UTC) Received: from ender.volumehost.net ([127.0.0.1]) by localhost (ender.volumehost.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05152-19 for ; Wed, 22 Feb 2006 19:05:53 +0000 (UTC) Received: from monster (ip70-178-175-2.ks.ks.cox.net [70.178.175.2]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ender.volumehost.net (Postfix) with ESMTP id 496D4CC49 for ; Wed, 22 Feb 2006 19:05:53 +0000 (UTC) From: "Boyd Stephen Smith Jr." To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] NTP problem Date: Wed, 22 Feb 2006 13:05:48 -0600 User-Agent: KMail/1.9.1 References: <43FC1376.9060907@gt.rr.com> <1140625753.21417.17.camel@localhost> <43FCAFA9.8080108@gt.rr.com> In-Reply-To: <43FCAFA9.8080108@gt.rr.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-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602221305.48615.bss03@volumehost.com> X-Virus-Scanned: amavisd-new at volumehost.net X-Archives-Salt: 18c5f0b6-ecd5-4dfe-b1eb-3eed6568dfcd X-Archives-Hash: 7b408e086ec0b16def970a3b0528e099 On Wednesday 22 February 2006 12:38, "Anthony E. Caudel" wrote about 'Re: [gentoo-user] NTP problem': > Brandon Enright wrote: > Well, overnight it only reset twice; - some improvement! > > Here is my complete ntp.conf: > # Name of the servers ntpd should sync with > # Please respect the access policy as stated by the responsible person. > #server ntp.example.tld iburst > > server pool.ntp.org This chooses a single random server from the pool to sync with, which is probably not /exactly/ what you want. You have a few alternatives: 1) Change "server" to "servers". Then, ntpd will use all the IPs associated with the domain name. As part of the process of syncing it will invalidate peers that have long or volatile round-trip times. It will, however, try to connect to 100s (IIRC) of IPs initially. 2) Use: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org In this case, the daemon will only use the first address from each domain name. .pool.ntp.org (for n = 0-9, IIRC) resolves to the same addresses as pool.ntp.org, but the primary address you get back is different each time. (I believe the . prefix is an attempt to prevent local caching, which would be a problem if you just repeated your server line 3 times.) You'll get better times syncing off multiple servers because the daemon can use some statistics to remove some of the network latency issues. However, you could still get a "bad draw" and get 3 servers far away from you. 3) Follow this comment from *your* .conf file: > # A good way to get servers for your machine is: > # netselect -s 3 pool.ntp.org netselect is available from portage, and I think it's generally installed during your gentoo install as a dependency of mirrorselect. In any case, you can use it to find 3 (or however many you want to use) servers close to you. Unfortunately, with this method, if better peers are added to the pool, the network topology changes, or anything else to invalidate the quality of the peers you pick, ntpd won't be able to automagically pick better ones. Also, for any of these options, you should note the geographic sub-pools that are available. I use us.pool.ntp.org. For (1) this will reduce the number of IPs initially connected to, for (2) it will increase the chance that you don't get a bad draw (because, generally, geographically closer is closer on the network), for (3) ... Well, actually for 3 you might as well pick the best ones from the entire pool. -- Boyd Stephen Smith Jr. bss03@volumehost.com ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list