openrc-discuss

Re: forcing nfs init script to kick off first

Roy Marples

Sat Jul 25 00:54:15 2009

On Friday 17 July 2009 00:25:15 James wrote:
> 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?

If you're using PXE, then / should be NFS correct? So why do you need the 
netmount script in the image as /etc/conf.d should be on /?

>
> 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.

Well, if you insist on starting netmount as early as, you could try this

rc_netmount_before="*"

Thanks

Roy

References:
forcing nfs init script to kick off firstJames
Archive administrator: postmaster@marples.name