when net.eth0 or any other eth device hasn't been started yet, I can't start it using "net.eth0 restart". That would be nice. Also when I use dhcp and try to boot without a network cable plugged in, I can't cancel the dhcp lookup (which takes about 2-3 min) with C-c. So I have to wait for it to finish. This is very annoying because at home I use 192.168.1.6 and at work I use dhcp and if I forget to change it when I go home I have to wait 2-3 min. Please fix this :-)
> when net.eth0 or any other eth device hasn't been started yet, I can't start it > using "net.eth0 restart". That would be nice. How so ? If it havent been started, do : # /etc/init.d/net.eth0 start If the service died, but are marked as started, do : # /etc/init.d/net.eth0 zap start For all availible options, run: # /etc/init.d/net.eth0 Donny, know anything about dhcp ?
he cant cntrl-c *any* initscript. and neither can the rest of us. i dont see any problem :)
during boot i meant of course.
I know I must use start to start it ;-) but what I meant was that the script could be changed so that when it hasn't been started yet restart tries to start it instead of giving me this lame error ;) A lot of other init script does this. About the C-c: FreeBSD and debian can do it. Why can't gentoo?
Sounds to me like the default DHCPCD time-out needs to be changed, so that the init script doesn't spend 2-3 minutes waiting for a response. Also, this bug probably doesn't belong in the Portage component :-)
The restart even if stopped have been fixed in later baselayout versions. As for the timeout, add it to dhcpcd options ?
yes, i'd suggest adding like '-i 20' to the dhcpcd options default is 60 seconds :(
*** Bug 16665 has been marked as a duplicate of this bug. ***
seems like it's simply problem, but gentoo develeper does'nt want to fix it. Why?
azarah is a busy man, leave him be
fixed in latest binutils
