Date: Sun, 14 Jan 2001 02:53:55 +0200 (IST) From: Roman Shterenzon <roman@harmonic.co.il> To: Antony T Curtis <antony@abacus.co.uk> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bug in NFSv3 client Message-ID: <979433635.3a60f8a32794f@webmail.harmonic.co.il> In-Reply-To: <3A5EF8A5.BC2E0AFD@abacus.co.uk> References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> <200101032308.f03N84f51776@earth.backplane.com> <3A5EF8A5.BC2E0AFD@abacus.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Antony T Curtis <antony@abacus.co.uk>: > Matt Dillon wrote: > > > > Bleh. I'm wrong twice. Don't bother with either patch. The > version > > is supposed to be 8 bytes. Scrap both patches. > > > > I'll have to look into this some more. There is definitely some > > weirdness in the NFS code. It could be the VATTR_NULL() call on > the > > server side that is broken. > > > > -Matt > > Is FreeBSD's nfsd locking still broken? > Yes, AFAIK it's still not implemented. You can search the archives to find some university version of nfs.lockd which may or may not work. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?979433635.3a60f8a32794f>