Date: Mon, 22 Nov 1999 15:08:23 -0500 From: "David E. Cross" <crossd@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: Ok, that's it, enough is enough! (rpc.lockd) Message-ID: <199911222015.PAA74002@cs.rpi.edu>
next in thread | raw e-mail | index | archive | help
Ok... I have *had* it with the meta, but not really, lockd. Are there any kernel issues with correctly implimenting rpc.lockd? How can I take a filehandle and map it into a filename, with path, so I may open it and lock it on the server? Are there any protocol specs? I downloaded the RFC for version 4 nlm (which we do not supoprt at *all*), but it only lists diffs to the version 3 spec, which I cannot find, and the source is not a whole lot of help on this issue. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 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-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911222015.PAA74002>