From owner-freebsd-current@FreeBSD.ORG Sun Mar 8 20:46:59 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F422C10656C5 for ; Sun, 8 Mar 2009 20:46:58 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id 83E6C8FC1C for ; Sun, 8 Mar 2009 20:46:58 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.2/8.14.2) with ESMTP id n28KkvNR005495; Sun, 8 Mar 2009 16:46:57 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.2/8.13.8/Submit) id n28Kkvfn005494; Sun, 8 Mar 2009 16:46:57 -0400 (EDT) (envelope-from wollman) Date: Sun, 8 Mar 2009 16:46:57 -0400 (EDT) From: Garrett Wollman Message-Id: <200903082046.n28Kkvfn005494@hergotha.csail.mit.edu> To: sam@freebsd.org X-Newsgroups: mit.lcs.mail.freebsd-current In-Reply-To: <49B410E0.4030803@freebsd.org> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> <20090303180307.GA11134@lor.one-eyed-alien.net> <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com> <20090304164953.GB1209@lor.one-eyed-alien.net> <49B397A4.8090508@gmail.com> <20090308180934.GA9147@lor.one-eyed-alien.net> Organization: None X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Sun, 08 Mar 2009 16:46:57 -0400 (EDT) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hergotha.csail.mit.edu X-Mailman-Approved-At: Sun, 08 Mar 2009 20:51:50 +0000 Cc: , current@freebsd.org Subject: Re: The rc.d mess strikes back 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: Sun, 08 Mar 2009 20:46:59 -0000 In <49B410E0.4030803@freebsd.org>, Sam Leffler writes: >wpa is typically not the issue unless wpa-eapol is involved (in which >case you need to negotiate with a backend authentication server). I hesitate to bring this up, but I've certainly had an issue for a long time that waiting for the default route doesn't solve -- the machines in question are configured statically. The problem is most pronounced with certain GigE interfaces that take a very long time to initialize, but happens on any network using the default Spanning Tree parameters. (Using DHCP would actually help with this, since you can't get a DHCP response until your port has moved into FORWARDING state, but one of the machines in question is the DHCP server, so that's not an option.) Because named no longer waits for a root server to be accessible when it starts, lots of daemons will get started, be unable to resolve names in their configuration files, and fail, before the network interface is even working. (ntpd is a particular problem in this case, because it doesn't exit when there are no associations configured, and it also does its name resolution asynchronously, so you can have ntpd come up and appear to be working, but completely unsynchronized.) I've generally solved this by hacking a little script into the order just after named to hold back the boot until named is able to resolve an external hostname. -GAWollman