rc sequencing issue / mountcritremote

[Tuc at T-B-O-H]

Hi,

	I'm having a bit of a problem with the sequencing of the rc when
it relates to "mountcritremote".

	Right now, the /etc/rc script performs :

files=`rcorder ${skip} /etc/rc.d/* 2>/dev/null`

	to determine in what order to start all the services. As it
stands now, the sequence looks like :


[...]
/etc/rc.d/route6d
/etc/rc.d/mrouted
/etc/rc.d/routed
/etc/rc.d/NETWORKING
/etc/rc.d/devd

/etc/rc.d/mountcritremote

/etc/rc.d/syslogd
/etc/rc.d/savecore
/etc/rc.d/SERVERS
/etc/rc.d/named
/etc/rc.d/ntpdate
/etc/rc.d/rpcbind
[...]

	The problem I'm having is that when it attempts to remotely
mount the NFS filesystem I need, there are no support programs
running, namely (I THINK) :

/etc/rc.d/rpcbind
/etc/rc.d/nfsclient
/etc/rc.d/mountd
/etc/rc.d/nfsd
/etc/rc.d/nfslocking

	It looks like nfsd could force some of this, but it
probably would be better that it ran properly.

	If I override the /etc/rc line to be something like

files=`cat /etc/localrcorder.conf`

	And run the "rcorder -s nostart /etc/rc.d/* > 
/etc/localrcorder.conf" and put those 5 items before the
"/etc/rc.d/mountcritremote", I get 95% of the way there. 
At this point, "/etc/rc.d/named" isn't running, so using
a FQDN on the /etc/fstab doesn't work. If I change it to
an IP, then everything is perfect.

	My question is if somehow I'm not configuring my
system correctly, that it shouldn't be mounting the filesystem
I need at that time. The problem is, though, is I need
my filesystem mounted for "/etc/rc.d/syslogd", so seems like
a good enough time as any. If I am configuring it to do it at
the proper time, is there a reason the dependencies don't
currently have rpc/statd/lockd/etc running first?

		Thanks, Tuc