From owner-freebsd-current@FreeBSD.ORG Wed Aug 31 11:10:45 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5363416A41F for ; Wed, 31 Aug 2005 11:10:45 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1186043D46 for ; Wed, 31 Aug 2005 11:10:45 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 418AC46BD9 for ; Wed, 31 Aug 2005 07:10:44 -0400 (EDT) Date: Wed, 31 Aug 2005 12:10:44 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: <20050831120730.B39418@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Ctrl-c abort of dhclient during rc.d start aborts all network configuration 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: Wed, 31 Aug 2005 11:10:45 -0000 I believe this is related to the new dhclient -- when I run my notebook disconnected from the network, the boot pauses for about 15-20 seconds waiting for a link on xl0. Being impatient when booting in airports just before my flight, I like to hit Ctrl-C and abort it, since I know that there will be no link. In the old world order, this was fine, dhclient was simply killed and all was good. In the new world order, it kills all of the netif startup script, and for some reason (ordering related, presumably), this prevents 127.0.0.1 from being configured on lo0, which causes a number of applications to die, since 0.0.0.0 cannot be bound. It sounds like a couple of things are unfortunate here: (1) It would be good to configure lo0 first. (2) If a dhclient is ctrl-c'd, it would be nice if the rest of the network configuration continued. The printing of '.'s in dhclient is also a bit excessive. Robert N M Watson