Date: Tue, 9 Mar 2004 17:51:23 -0500 (EST) From: "Jason M. Leonard" <fuzz@ldc.upenn.edu> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-questions@freebsd.org Subject: Re: NFS and file-locking Message-ID: <20040309174631.N78793@lorax.ldc.upenn.edu> In-Reply-To: <20040309222400.GA75180@xor.obsecurity.org> References: <20040309215001.GA28538@axion01.tphys.physik.uni-tuebingen.de> <20040309170935.Y78249@lorax.ldc.upenn.edu> <20040309222400.GA75180@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 Mar 2004, Kris Kennaway wrote: > On Tue, Mar 09, 2004 at 05:19:42PM -0500, Jason M. Leonard wrote: > > > > On Tue, 9 Mar 2004, Kris Kennaway wrote: > > > > > On Tue, Mar 09, 2004 at 10:50:01PM +0100, Dominik Epple wrote: > > > > Hi, > > > > > > > > can anyone please give me some short information (or a pointer to it) > > > > about the status of file locking over NFS with FreeBSD clients and > > > > different servers (e.g. FreeBSD, OpenBSD, linux). > > > > > > FreeBSD 5 has working NFS locking (rpc.lockd) support. Linux is > > > broken and will not interoperate with FreeBSD unless you apply the > > > patch in PR kern/56461. > > > > rpc.lockd support is not entirely stable; see PR bin/61718. > > > > I am always able to force the described problem to happen between two > > 5.2.x machines by using the file locking test from the > > /usr/ports/mail/procmail installation. When it asks for additional > > locations to test file locking, give it a remote NFS destination and watch > > things break. > > Any reason this important test case is not listed in the PR? ;-) Oops, I assumed (d'oh!) that it was common knowledge. I also hadn't read the PR in a while; it looks like a patch was submitted a week ago that may solve the problem. :Fuzz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040309174631.N78793>