From owner-cvs-all@FreeBSD.ORG Mon Jul 28 11:41:12 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 898AC37B405 for ; Mon, 28 Jul 2003 11:41:12 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id B128E43FBD for ; Mon, 28 Jul 2003 11:41:10 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 53130 invoked by uid 1000); 28 Jul 2003 18:41:11 -0000 Date: Mon, 28 Jul 2003 11:41:11 -0700 (PDT) From: Nate Lawson To: Robert Watson In-Reply-To: Message-ID: <20030728113909.C53096@root.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: Martin Blapp cc: cvs-all@FreeBSD.org cc: src-committers@FreeBSD.org Subject: Re: cvs commit: src/etc/defaults rc.conf src/etc/rc.d dhclient X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2003 18:41:13 -0000 On Mon, 28 Jul 2003, Robert Watson wrote: > On Mon, 28 Jul 2003, Martin Blapp wrote: > > > Forgive me for not having time to go read the dhclient details, but > > > unfortunately I'm a bit pressed for time this morning. I just wanted to > > > confirm that dhclient gives a "first reasonable try" if the link is up in > > > this situation, rather than immediately backgrounding, since some services > > > will behave poorly if they don't find IP addresses, etc. Ie., this > > > operates like the NFS mount background option: "If at first you don't > > > succeed, try again on your *own* time". > > > > > > The services I have in mind are, indeed, network file system mounting, > > > sandboxed named, sendmail, and third party applications that like to bind > > > each IP address manually rather than use INADDR_ANY. > > > > and natd (where I've fixed the rc script to work with the dhclient case) > > > > The problem here is that a box not connected to lan with dhcp hangs till > > you press CTRL C. > > Well, or a minute or two, but I agree that in the notebook disconnected > from a network case, that's not much fun. There is no reason to wait if there is no network link. If configuring via dhclient and no link on that interface, there is no way you are getting a lease, no matter how long you wait. It's better to go into the background if there is no link. If there is a link, the normal dhcp timeouts should be honored and dhclient should not allow booting to continue until it is done with the protocol. -Nate