It takes at least a minute for the net.eth0 init script to try to bring eth0 up, before it gives up. This is not a duplicate of 12382, because that was marked fixed, and this bug isn't fixed. I have binutils-2.14.90.0.7-r3 and baselayout-1.8.6.12-r3. Reproducible: Always Steps to Reproduce: 1. 2. 3.
are you using dhcp ?
Yes.
then set the timeout option of dhcpcd to be lower
This bug is not invalid. It is a problem with the Gentoo startup scripts, and if you won't fix it, then mark it WONTFIX, but it isn't invalid. I don't want my DHCP timeout to be lower in general, I just want the net.eth0 init script to time out faster. Other Linux distributions use a smaller timeout in the init scripts than when calling dhcpcd manually, and it makes sense - you can't cancel it.
no, what you're talking about is trying to make the init scripts hold your hand a little bit more with dhcp, it's up to you to specify the paramters (including timeout) some people actually need that 60 seconds (or even more) to get their dhcp information so killing it in a short time in the init script is just wrong if you want a smaller timeout then add the paramter to dhcpcd_ethX and that's the end of it
Here's what I did to solve this: Add this to setup_env(): if mii-diag -s ${iface} 2>/dev/null >/dev/null; then link_IFACE="yes" else link_IFACE="no" fi And add this to iface_start(): if [ "${link_IFACE}" == "yes" ] then /sbin/dhcpcd ${dhcpcd_IFACE} ${IFACE} >/dev/null || { retval=$? eend ${retval} "Failed to bring ${IFACE} up" return ${retval} } fi This will not attempt to bring up the dhcp if there's no link on the interface. Works great for me.
