network boot and rpc.statd

[KShots]

I've finally made a breakthrough in getting file locking to work under a FreeBSD NFS server and a gentoo client... but now I'm at a loss on how to automate this during boot-up.

rpc.statd must be running for rpc.lockd (which is called as needed) to function.

Unfortunately, I cannot think of a way to run rpc.statd before the kernel loads the root file system... is there a way to load it, then unmount the root fs, then re-mount the root fs without the nolock option?

Or am I spinning my wheels, meaning rpc.statd will function after everything mounts - it just needs to be up before the 1st lock request (which would make it an EARLY boot service)?
_________________
Life without passion is death in disguise

[erik258]

i usually have problems only if i try to interfere with the mounting process during boot on my diskless problems. leave them alone, and they do fine.

are they locking up for you?
_________________
Configuring a Firewall? Try my iptables configuration
LinuxCommando.com is my blog for linux-related scraps and tidbits. Stop by for a visit!

[KShots]

Actually, I was experimenting during the install phase. During the install, if I simply start portmap and then mount my root fs over nfs, it succeeds, but then file locks don't work (which screws up portage and probably several other things). Previously, to get around this, I was mounting with the nolock option... which is dangerous, but it works. However, recently I found that if I have rpc.statd running, file locking actually seems to work.

Further experimentation has shown that rpc.statd may be started after mounting as well as before, so I can probably limp by with an init script (I think nfsmount actually starts rpc.statd).
_________________
Life without passion is death in disguise

[erik258]