From owner-freebsd-current@FreeBSD.ORG Tue Mar 31 20:39:15 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30CD41065687 for ; Tue, 31 Mar 2009 20:39:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id BCAC98FC0C for ; Tue, 31 Mar 2009 20:39:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 10866 invoked by uid 399); 31 Mar 2009 20:39:08 -0000 Received: from localhost (HELO 192-168-15-100.nohostname) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 31 Mar 2009 20:39:08 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <49D278BA.6070705@FreeBSD.org> Date: Tue, 31 Mar 2009 13:10:34 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.21 (X11/20090321) MIME-Version: 1.0 To: Alexander Leidinger References: <49D1B261.6010406@FreeBSD.org> <20090331101454.16983mt8x4ru2xog@webmail.leidinger.net> In-Reply-To: <20090331101454.16983mt8x4ru2xog@webmail.leidinger.net> X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: New rc.d/named features for testing: auto-forwarding and wait on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 20:39:15 -0000 Alexander Leidinger wrote: > Quoting Doug Barton (from Mon, 30 Mar 2009 23:04:17 > -0700): > >> There has been some discussion recently about the idea of adding an >> option for the rc.d startup process to wait until name resolution >> comes on line. (There is also room for a more general "wait for the >> network to come on line" option, but I chose to focus on the named >> version since my time is limited atm.) > > I assume this is opt-in, and not on by default Careful reading of my post, or 2 seconds spent looking at the patch will answer this for you. > At which place in the startup would this wait? This would be answered by looking at the patch as well, but since I'm a nice guy I'll tell you that it waits right after named is started. On my system with essentially the default "local resolver" configuration plus a few things added the delay waiting for the host command to complete is almost unnoticeable. Doug -- This .signature sanitized for your protection