From owner-freebsd-hackers Mon Nov 22 12:48:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CFD5914BF7 for ; Mon, 22 Nov 1999 12:48:57 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id NAA04071; Mon, 22 Nov 1999 13:14:24 -0800 (PST) Date: Mon, 22 Nov 1999 13:14:24 -0800 (PST) From: Alfred Perlstein To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: <199911222015.PAA74002@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, David E. Cross wrote: > 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. here's a url to some of the stuff I have in the works before work utterly consumed me: http://www.freebsd.org/~alfred/misc-patches/ (lockd.diff) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message