Date: Mon, 28 Jul 2003 15:00:11 +0200 (CEST) From: Martin Blapp <mb@imp.ch> To: Robert Watson <rwatson@FreeBSD.org> Cc: src-committers@FreeBSD.org Subject: Re: cvs commit: src/etc/defaults rc.conf src/etc/rc.d dhclient Message-ID: <20030728145421.O41136@cvs.imp.ch> In-Reply-To: <Pine.NEB.3.96L.1030728084636.56734D-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1030728084636.56734D-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > This is something we'll probably want to play by ear -- trading off boot > time and making sure that the right services are there to support various > kinds of activities. I think part of the real solution is likely to > improve the behavior of some of our applications in the presence of > changing network configuration. A few more apps probably need to learn > about routing sockets so they can pick up IP address change notifications, > interface arrival/departure, etc. That would make sense. The same thing happens if you use zebra (gated replacement). The system does not behave very well if you don't add manually about 20 sleep seconds in the rc script ! With dhclient, the problem is really not that bad. Within 3 seconds you normally get the lease. Which means, that we could add a script which checks, if the dhclient interface has a 0.0.0.0 adress (or even check if the default route is set), and then sleeps and blocks the boot process. The applications which really need this could rely then on the script. And all other setups without this would boot faster. Just some thoughts ... Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030728145421.O41136>