Date: Thu, 14 Dec 2000 17:45:15 -0500 From: "David E. Cross" <crossd@cs.rpi.edu> To: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>, Carsten Urbach <Carsten.Urbach@physik.fu-berlin.de> Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? Message-ID: <200012142245.RAA69128@cs.rpi.edu> In-Reply-To: Message from Axel Thimm <Axel.Thimm@physik.fu-berlin.de> of "Thu, 14 Dec 2000 23:07:56 %2B0100." <20001214230756.A13794@pua.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
I pruned the Cc: list a bit... One of the email messages that you quoted has the URL for the latest development of the lockd code. As far as tests go it appears to be mostly complete (there appears to be an issue with RPC64 on little endian machines, but I have not yet had a chance to crawl through the librpc code). As for "client" vs. "server", that is quite tricky.... since WRT NFS locking they are both client and server. The "server" side is done and requires no modifcations to the kernel. However a FreeBSD kernel is still unable to acquire an NFS lock. This latter case is quite likely what your users are seeing the affects of. In the end: the code is there and available for those who want to test and play with it. It has not been committed because it is still "broken". I could do it to -current or make it a port, if someone were to tell me that it would be "ok" to do so. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012142245.RAA69128>