From owner-freebsd-questions Fri May 29 14:09:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02896 for freebsd-questions-outgoing; Fri, 29 May 1998 14:09:00 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02849 for ; Fri, 29 May 1998 14:08:43 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id NAA00714; Fri, 29 May 1998 13:51:48 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Fri, 29 May 1998 13:51:48 -0700 (PDT) From: Doug White Reply-To: Doug White To: ursa@cris.com cc: "'questions@FreeBSD.org'" Subject: Re: NFS locking In-Reply-To: <0545563AD3A8D011B35000805FBB53A54D3C3F@ptexcatl01.premtec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 May 1998, Grammas, August wrote: One of the hackers may have to reply to this, I'll do the best I can. > I need information on IF / HOW NFS file locking is implimented in > FreeBSD. I am not asking > for an explation, but where in the doco I will find information on NFS > file locking. The problem is that the NFS locking spec isn't published, so we have to reverse engineer it. In addition there are some serious issues with the whole idea. We do have (limited, buggy) support for client locking only. > Please send any replies to ursa@cris.com and NOT to > agrammas@premtec.com. Then please set this as your reply-to or use your own account :) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message