(Similar to #266386, but different resolution suggested.) Various server init scripts (including, e.g., sshd and apache2) list "need net", meaning that if all Ethernet interfaces go down, the servers are killed--and even worse, the services are not restarted when the interfaces come back up. For most of these packages, there is absolutely no need for an external network interface for them to work properly; net.lo is thoroughly sufficient. This is especially problematic on laptops, where network interfaces may come up and down frequently but users want to run a development Web server or SSH. Reproducible: Always Steps to Reproduce: 1. start any server listing "need net" 2. shut down all net.eth? services 3. restart net.eth? services Actual Results: Servers are killed off and not restarted. Expected Results: Servers should not be killed, or at least those that are listed in the current runlevel should be restarted. For most of these packages, "need net" makes no sense. "use net" would have the desired effect of bringing up networking first and would keep the servers from being shut down unnecessarily.
Apps that bind to specific IP addresses on start do possibly need to be restarted with network interface up/down flips that involve IP changes.
*** This bug has been marked as a duplicate of bug 439092 ***
