From owner-freebsd-stable@FreeBSD.ORG Wed Dec 15 00:47:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23D5B10656A5 for ; Wed, 15 Dec 2010 00:47:15 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id C42B28FC22 for ; Wed, 15 Dec 2010 00:47:14 +0000 (UTC) Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta10.westchester.pa.mail.comcast.net with comcast id iz671f0051YDfWL5ACnE1Y; Wed, 15 Dec 2010 00:47:14 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta20.westchester.pa.mail.comcast.net with comcast id jCnD1f00D3LrwQ23gCnEMm; Wed, 15 Dec 2010 00:47:14 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 252849B427; Tue, 14 Dec 2010 16:47:12 -0800 (PST) Date: Tue, 14 Dec 2010 16:47:12 -0800 From: Jeremy Chadwick To: Dan Allen Message-ID: <20101215004712.GA56065@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: dougb@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: ntpd fails on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2010 00:47:15 -0000 On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > Recently my network connection now is setup AFTER ntpd is launched rather than before. > > So when ntpd starts there is no net connection and it gives up. > > I read /usr/src/UPDATING but nothing is mentioned about a change in boot order. > > Any ideas? This issue has been discussed pretty thoroughly in the past. There's no official solution, but there is an rc.d script I wrote which addresses this shortcoming. Nothing related to the "boot order" has changed, but network drivers and overall methodology has changed. Anyway, many people are using the below with success. http://jdc.parodius.com/freebsd/netwait Official patches, including the rc.conf(5) change I propose: http://jdc.parodius.com/freebsd/netwait_patches/ Example usage (in rc.conf): netwait_enable="yes" netwait_ip="4.2.2.1 4.2.2.2" netwait_if="em0" For what these variables mean, please see the script itself. They are thoroughly documented. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |