I was rebuilding my system with new use flag debug, cause some KDE apps have a nasty habit of crashing. I stopped it somewhere midway. Then when I rebooted, dhcpcd would spit a lot of debug messages, though no errors or warnings or so, and wouldn't finish. The system was perfectly responsive. After remerging dhcpcd without debugging use flag I could boot fine again.
Portage 2.1_pre4-r1 (default-linux/amd64/2005.1, gcc-3.4.5-vanilla, glibc-2.3.6-r2, 2.6.15-gentoo-r3 x86_64)
System uname: 2.6.15-gentoo-r3 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.12.0_pre16
dev-lang/python: 2.3.5, 2.4.2-r1
sys-devel/autoconf: 2.13, 2.59-r7
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
CFLAGS="-march=k8 -pipe -O2"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/texmf/web2c /etc/env.d"
CXXFLAGS="-march=k8 -pipe -O2"
FEATURES="autoconfig distlocks sandbox sfperms strict"
Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
The dhcpcd ebuild warns you about the debug USE flag.
debug should be enabled on a per ebuild basis, not a global basis. In dhcpcd's case it is great for debugging DHCP server responses but it does not work as a dhcp client itself.
*** Bug 149732 has been marked as a duplicate of this bug. ***
Perhaps the USE flag could be changed to something more fitting, since the resulting behavior is different from every other ebuild?
In any case, it should not hang boot indefinitely without allowing interruption. There should be some sort of forced timeout in the init script.
(In reply to comment #3)
> Perhaps the USE flag could be changed to something more fitting, since the
> resulting behavior is different from every other ebuild?
> In any case, it should not hang boot indefinitely without allowing
> interruption. There should be some sort of forced timeout in the init script.
The debug use flag is used to debug dhcp client interaction with a dhcp server. The downside is that this means that it doesn't actually work as a dhcp client.
The ebuild warns you about this.
Thank you for repeating yourself unecessarily. I'll do the same, and hopefully you actually read what I have to say this time.
Since the debug flag causes broken behavior which requires a warning that is easily missed, perhaps the USE flag could be changed to something else for this package, i.e. debugonly.
Furthermore, no matter what the warning, the init script should not be able to hang the system boot process rendering the system completely unusable. If a debug dhcpcd is built, then the init script needs to abort after a timeout, say, 60 seconds. This needs addressed as it's very easily to make your system unusable. ebuild warnings are very commonly overlooked and are not an acceptable substitute for a proper fix.
dhcpcd-3 no longer does this, so fixed