Re: [gentoo-user] Can I make dhcpcd run in background when trying to get an ip address?

[Luk van den Borne]

Maybe you should have a look at ifplugd. It will background the networking
part and bring up those interfaces that are actually plugged in.

Luk van den Borne

On 9/25/05, Iain Buchanan <iaindb@××××××××××××.au> wrote:
>
> On Sat, 2005-09-24 at 20:52 -0700, michael@×××××××××××××.com wrote:
> > I have a computer with both a wired and wireless network card. At home I
> > use the wired connection, but when out I use the wireless.
> [snip]
> > Is there some way I can have dhcpcd to run in the background, and to
> > provide an IP address to my interface when it gets a response from the
> > server? I seem to remember busybox had script that did this; is there a
> > general solution?
>
> The first thing that comes to mind is to set
> RC_PARALLEL_STARTUP="yes"
> in /etc/conf.d/rc
>
> However, lots of things rely on the net.* scripts before they start.
> Have a look at the output of
> `egrep need.*net /etc/init.d/*`
> and you'll see every service that will wait for your network script to
> start (which means waiting for a dhcp response)
>
> The second thing that came to my mind, and this would probably rely on
> you only getting a dhcp for the wireless, and not the wired lan, would
> be to "roll your own" /etc/init.d/net.eth1 script. Make it exactly the
> same as /etc/init.d/net.lo, but in the depend() function, add something
> like "provide mywireless". This, coupled with parallel startup, should
> mean that no other init script will require your net.eth1 connection and
> it can take time without holding other scripts up.
>
> I've never tried this idea, so it could be fundamentally flawed, but its
> just a thought!
>
> HTH,
> --
> Iain Buchanan <iaindb@××××××××××××.au>
>
> --
> gentoo-user@g.o mailing list
>
>