Date: Tue, 14 Dec 2010 16:47:12 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Dan Allen <danallen46@airwired.net> Cc: dougb@freebsd.org, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: ntpd fails on boot Message-ID: <20101215004712.GA56065@icarus.home.lan> In-Reply-To: <F211F762-1572-4509-9A3D-807E0595C1CD@airwired.net> References: <F211F762-1572-4509-9A3D-807E0595C1CD@airwired.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101215004712.GA56065>