This service fails to start on a my machine with a nfs network root mounted filesystem:
Service `nfsmount' needs non existent service `net'
that makes no sense. nfsmount needs the network, so it needs to be started after the network is up.
i'm not sure if "after net" will fly in terms of shutting down. openrc has to know that it can't turn off the network before it stops the nfsmount init.d.
The problem is that depending on the "net" virtual can't and doesn't
tell you when the route to the server where the file system is stored is
actually active. You get a better dependency by having users set
rc_need="net.foo" or whatever they need in their /etc/conf.d/nfsmount
(In reply to comment #2)
yes, you get "better" resolution, but a default of ignoring net altogether is an awful user experience
"after net" will be a fine default for startup, but i'm not sure about shutdown without actually reading code/testing. do you know off the top of your head William ?
After net should work.
Actually what I would do is put it in the conf.d file like this:
Then explain to the user with documentation in there that they
can/should adjust it.
Considering what you just said, you may want to get this to go to stable
asap after openrc-0.11.5. I just filed a stablereq for it because newer
OpenRC is needed in stable for several reasons now.
(In reply to comment #4)
that works for me. the netmount script with openrc should do the same thing as its current default (not depending on net at all) is wrong.
should be all set now in the tree; thanks for the report!
Commit message: Move net usage to conf.d (defaults are unchanged)