> I'm attempting to use the "stable" kernel-2.2.12 with knfsd-4.7.1 and
> knfsd-lock-4.7.1mdk and its a mess. Most of the problems seem
> assosciated with nfs. So far I've seen the following:
>
> 1. The lockd process won't start - when I run rpc.lockd I get the
> message "lockdsvc: invalid argument"
Have you tried throwing out the knfsd-lock patch, and just running
with the stock lockd stuff (no userland rpc.lockd required)?
The userland rpc.lockd + kernel patch should really only be needed as
a hack for NFSroot systems and for people who can't afford to start
rpc.statd before mounting an NFS partition.
> 2. Directories mounted with the automounter will just "go away",
> usually in such a way that tasks referencing them hang.
Which automounter is this? I have no such problems with 'autofs'.
If you're using am-utils or amd, first try using autofs as an
alternative. (You will lose the '/net' stuff, but since you said that
didn't work...) If that shows your problem to be with am-utils/amd
then please contact the maintainer of that package.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/