Messages in this thread |  | | Date | Tue, 10 Jun 2003 11:17:07 +0100 (BST) | From | Bob Vickers <> | Subject | Re: Locking NFS files on kernels 2.4.19 and 2.4.20 |
| |
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 kernel.
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 too.
Bob
On 9 Jun 2003, Trond Myklebust wrote:
> >>>>> " " == Bob Vickers <bobv@cs.rhul.ac.uk> 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 R.Vickers@cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |