From owner-freebsd-stable Wed May 24 12: 1:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by hub.freebsd.org (Postfix) with ESMTP id 05B6337BD49 for ; Wed, 24 May 2000 12:01:09 -0700 (PDT) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.0) with SMTP id FAA05846; Thu, 25 May 2000 05:00:05 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 25 May 2000 05:00:04 +1000 (EST) From: Ian Smith Reply-To: Ian Smith To: Glen Gross Cc: "'Lev Serebryakov'" , All Subject: RE: ntpdate could not sync time from any server. In-Reply-To: <01BFC568.F898D720.ggross@symark.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 May 2000, Glen Gross wrote: (re message: 'no server suitable for synchronization found') > I have had the same experience, with a DSL line. I don't know if > ntpdate requires the time to be within a certain threshold before > it will sync or not. Yes, it does; -t sets the time ntpdate will wait for a valid response. Still get one of these logged once every few days when upstream PPP link is extra heavily used, but used to get it much more often before using: ntpdate -t 2.4 -s ntp.ml.csiro.au ntp.cs.mu.oz.au judge.lis.net.au That's 2.4 seconds. man ntpdate isn't exactly clear re the unit format, but it does say that the default of 1 second is suitable for a LAN. Cheers, Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message