After executing /etc/init.d/net.eth0 stop (primarily to easily remove net.eth0 from the route table so my 802.11 card can take over) the system immediately shuts down all net dependent services. However, 802.11 is still ready to run those services. This is a minor bug, of course, because running "ifconfig eth0 down" will result in the desired behavior without the problem behavior.
`/etc/init.d/net.eth0 pause`
*** Bug 26425 has been marked as a duplicate of this bug. ***
martin: you claimed this worked but it doesnt ;) if you have 'net.lo' and 'net.eth0' running, then stopping 'net.eth0' should not nuke all services dependent on net
*** Bug 26681 has been marked as a duplicate of this bug. ***
Reading the previous comments here, it does look like I've got lo running: # ip ro ls 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.18 127.0.0.0/8 via 127.0.0.1 dev lo scope link But net.eth0 stop will stop apache and mysqld. I repeat what I said in the duplicate bug report (somehow searching for net.eth0 did not find the original one): apache and mysqld are _not_ in any formal sense net dependent. Mysqld has perfectly reasonable uses in a stand-alone system, and Apache can be used stand-alone too - for instance as a front-end for scripts accessing Mysqld databases, or to view HTML pages being authored. There's no way mysqld or apache should ever depend on having your network up, or shut down just because a network interface is being taken down. There are certainly uses that are for the network, where one doesn't care if mysqld or apache is running if the network isn't there, but the operative phrase there is "doesn't care."
Actually, I believe Apache *is* net dependent, even if that 'net' is 'lo'...
I'll yield to Luke on the lo-down. (Which means that net.eth0 still shouldn't care.) But MySQL? If your database is doing something that it requires the net for (other than some side task like replication) you've probably got a security problem.
umm apache will bind to *:80 so it doesnt matter what net.* you have up
Come on guys. Let net.lo provide "net" or remove the "need net" dependancies from the startup scripts which don't need it (like apache and stuff) but DO SOMETHING, please... Until then, I can't do the PHP development on my notebook (when it's unplugged from the network while booting -> it cannot get DHCP answer -> net.eth0 startup fails -> apache2 refuses to start) and that's bad since PHP development is what I get money for... :-) Of course I have my scripts modified but every upstream (Gentoo) update forces me to do that research again and again... :-( Thanks... Radek
should be configurable now # Set to "yes" if the default behaviour of at least one net.* # service starting beside net.lo is NOT enouth to consider # the 'net' dependency up and running. RC_NET_STRICT_CHECKING="no"
