Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.

[Patrice Bouvard]

Le Sun, 28 Jan 2007 00:51:57 -0500,
James Lockie <bjlockie@××××××.ca> a écrit :

> Richard Watson wrote:
> > Hi, I recently upgraded my system with emerge -uDN world. Afterwards I found that net.eth0 was grabbing my firewire port (ieee1394) and I needed to create net.eth2 for my NIC as net.eth1 was being assigned to my wireless. My problem is that although "rc-update show" indicates all my interfaces are NOT being loaded other than net.lo at boot (which is what I want) my system keeps trying to start net.eth0 net.eth1 net.eth2 in the " default" run level. Can anybody help? It's very frustrating waiting for these interfaces to try and connect before timing out.
> >
> > I've always run my network connection on this basis as Gentoo is on my laptop and depending where I am will determine which interface I want to use.
> >
> > Thanks, Richard
> >
> >
> rm /etc/init.d/net.eth0 && rm /etc/init.d/net.ath1
>

That's a solution. Unfortunately, not always the good one.


Richard : you should have a look at RC_PLUG_SERVICES in /etc/conf.d/rc


Another solution if you are dhcp-ing is (from /etc/conf.d/net.example) :

# For passing custom options to dhcpcd use something like the following.  This
# example reduces the timeout for retrieving an address from 60 seconds (the
# default) to 10 seconds.
#dhcpcd_eth0="-t 10"

But !!! Yes, there is a "but"... Be carefull. On some networks, it might takes a bit more than 10sec
to receive an dhcp answer.


-- 
Cordialement,
Patrice BOUVARD, Networks & Systems Engineer

-- 
gentoo-user@g.o mailing list