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 1F59gG-0008Vf-SZ for garchives@archives.gentoo.org; Fri, 03 Feb 2006 22:45:29 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k13MiREN021741; Fri, 3 Feb 2006 22:44:27 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 k13MeO0E009173 for ; Fri, 3 Feb 2006 22:40:24 GMT Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by smtp.gentoo.org with esmtp (Exim 4.54) id 1F59bL-0006V5-KC for gentoo-user@lists.gentoo.org; Fri, 03 Feb 2006 22:40:23 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1F59aw-0007u6-DF for gentoo-user@gentoo.org; Fri, 03 Feb 2006 23:39:58 +0100 Received: from adsl-68-74-146-31.dsl.emhril.ameritech.net ([68.74.146.31]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Feb 2006 23:39:58 +0100 Received: from reader by adsl-68-74-146-31.dsl.emhril.ameritech.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Feb 2006 23:39:58 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Harry Putnam Subject: [gentoo-user] Re: ntp won't synchronize Date: Fri, 03 Feb 2006 16:39:38 -0600 Organization: Still searching... Message-ID: <877j8crrrp.fsf@newsguy.com> References: <20060109192522.GA1519@sewage.sewage.fake> <20060203220645.GA23518@sewage.sewage.fake> 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-74-146-31.dsl.emhril.ameritech.net User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:Y/HCE55Z5NHqVLVmZc8MoaSKbOg= Sender: news X-Archives-Salt: 5c037672-23a8-4ce2-bc57-15f7b2638822 X-Archives-Hash: 375d3bc462ba3b380704ae773e0fcd8a matthew.garman@gmail.com writes: > On Wed, Feb 01, 2006 at 07:25:35PM +0000, James wrote: >> ntpq -p >> remote refid st t when poll reach delay offset jitter >> ============================================================================== >> ecoca.eed.usv.r 80.96.120.253 2 u 8 64 1 202.639 1436722 0.001 This won't help the above problem but it might help the overall situation. As I recall ntpd will not adjust the time above a certain threshold. I don't recall the threshold but its pretty low. I've found if I make ntp-client to run at boot time it sets the clock before ntpd gets to it and makes sure its below that threshold. Once the clock is below that threshold ntpd will keep it right (assuming its connecting with time servers) Throwing in my own question here. I'd never run ntpq -p before but now I did and now wondering what a dash before severname means. remote refid st t when poll reach delay offset jitter ============================================================================== [...] -atlas.jtan.com 128.4.40.12 3 u 488 1024 377 68.824 -11.85987.611 [...] I couldn't find any reference to it in man ntpq which is loaded with info. It refers the reader like this: For examples and usage, see the NTP Debugging Techniques page. But doesn't bother saying what that is supposed to be a page of. Also found this in there but its so cryptic I couldn't tell if this is what I was looking for or what it shows a dash being used at least. - outlyer The peer is discarded by the clustering algorithm as an outlyer. -- gentoo-user@gentoo.org mailing list