This is to track the service scripts which are using "need net"
Most of the time services do not really "need net", and this should be
The problem with having it is that bringing down one interface
automatically brings down the services that have "need net" in their
To test your service to see if it really needs net, do the following:
- bring down *all* of your network interfaces, including loopback.
- drop the "need net" line from your init script.
- bring up your service in its default configuration.
- If it comes up successfully, try cycling network interfaces and using
your service with different interfaces up and down. If it works, you
are done; commit your init script without the "need net" dependency.
- If it doesn't work, you will need to add documentation to your
conf.d/service file explaining to users how to tie your service to
which ever interface they are using it on with an rc_need line.
Feel free to contact me with questions.
Flameeyes wrote the following blog post concerning this issue:
*** Bug 444260 has been marked as a duplicate of this bug. ***
Please see https://bugs.gentoo.org/show_bug.cgi?id=444652 and let me know if it's related. Thanks.
*** Bug 447156 has been marked as a duplicate of this bug. ***
/etc/init.d/netmount is triggering NetworkManager (+dbus +....) to start without any "need net". Looks like a hidden "need net" in some dependency.
Created attachment 343152 [details]
sshd init script
sshd does not need "need net"
*** Bug 268688 has been marked as a duplicate of this bug. ***