openrc-discuss

forcing nfs init script to kick off first

James

Thu Jul 16 23:25:36 2009

All,

I'm setting up a PXE server / client infrastructure and have
everything working except for a minor hiccup. While I have netmount
configured to kick off in the boot runlevel, there are other daemons
in the boot runlevel which start *before* netmount. This poses a
problem as the /etc/conf.d directory is mounted via NFS and these
daemons cannot get to their configuration.

Is there a way to force netmount to start before any of the other
daemons in the boot runlevel?

I see in the /etc/rc.conf file that there's a section regarding boot orders:

# It's possible to define extra dependencies for services like so
#rc_config="/etc/foo"
#rc_need="openvpn"
#rc_use="net.eth0"
#rc_after="clock"
#rc_before="local"
#rc_provide="!net"

# You can also enable the above commands here for each service. Below is an
# example for service foo.
#rc_foo_config="/etc/foo"
#rc_foo_need="openvpn"
#rc_foo_after="clock"

I'm not sure what to change, though, in this file in order to ensure
netmount starts before other daemons.

Thoughts? :)

Thanks!
-j

Follow-Ups:
Re: forcing nfs init script to kick off firstRoy Marples
Re: forcing nfs init script to kick off firstJames
Archive administrator: postmaster@marples.name