Summary: | apache2 won't start without network | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Clock <clock> |
Component: | Current packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Clock
2005-04-27 10:13:45 UTC
RC_NET_STRICT_CHECKING="none" or "lo" in /etc/conf.d/rc should solve this (needs ~arch baselayout). *** Bug 103109 has been marked as a duplicate of this bug. *** The same happens with /etc/init.d/apache2 stop when the network cable is removed. This time it's the apachectl itself which hangs. I suggest checking if the DNS lookup can be turned off by some flag and if not, then a) making a gentoo-specific patch to get rid of this Apache's bloatware behaviour, or b) Writing Apache people to fix it, or c) Try apachectl and if it doesn't end in 3 seconds, killing it and if it doesn't die within 2 seconds, killing it with -9 This isn't realistic. Apache is a network service, and meant for running while connected to a fuctional network, not just localhost. If after you boot a network becomes available, it's not difficult to run /etc/init.d/apache2 start. In fact, I believe there are tools out there to do certain things when a wireless connection becomes available. |