Re: Locking NFS files on kernels 2.4.19 and 2.4.20

From: Bob Vickers (
Date: Tue Jun 10 2003 - 05:17:07 EST

Dear Trond,

Thank you very very much, that is it! rpc.statd was running on the server
but not the client. I have started it and it now works.

The stupid thing is I was really close to seeing this weeks ago, but got
confused by various ancient pieces of documentation and by the fact
that you don't need rpc.lockd any more because lockd is now part of the

And the high-level message is: starting SuSE 8.1 you need to type
   chkconfig nfslock on
if you want NFS locking to work on the client. And probably on the server


 On 9 Jun 2003, Trond Myklebust wrote:

> >>>>> " " == Bob Vickers <> writes:
> > I have recently upgraded some machines and have found that it
> > is no longer possible to lock files on NFS file systems. It is
> > definitely a client-side problem: upgraded clients could no
> > longer lock files on *any* NFS server (including Tru64 as well
> > as a variety of Linux servers).
> Two questions:
> Are you running statd on the client and server?
> if no, then you should...
> Does SuSE compile statd with or without the RESTRICTED_STATD flag?
> If the latter, then you'll need an extra kernel patch in order to
> allow the kernel NSM to use a reserved port. Something like the
> appended scheme...
> Cheers,
> Trond

Bob Vickers
Dept of Computer Science, Royal Holloway, University of London
Phone: +44 1784 443691

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:23 EST