From owner-freebsd-net@FreeBSD.ORG Fri Nov 26 00:47:15 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AD6A16A4CE; Fri, 26 Nov 2004 00:47:15 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86CF143D3F; Fri, 26 Nov 2004 00:47:15 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 7921C5C8F6; Thu, 25 Nov 2004 16:47:15 -0800 (PST) Date: Thu, 25 Nov 2004 16:47:15 -0800 From: Alfred Perlstein To: Bj?rn Gr?nvall , freebsd-net@FreeBSD.org, lennox@cs.columbia.edu, kris@FreeBSD.org, dnelson@allantgroup.com Message-ID: <20041126004715.GD69608@elvis.mu.org> References: <20041125201812.609e50f9@manian.sics.se> <20041125215225.GF733@empiric.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041125215225.GF733@empiric.icir.org> User-Agent: Mutt/1.4.2.1i Subject: Re: Linux compatible rpc.lockd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 00:47:15 -0000 * Bruce M Simpson [041125 13:53] wrote: > On Thu, Nov 25, 2004 at 08:18:12PM +0100, Bj?rn Gr?nvall wrote: > > I have made a patch to address PR kern/56461, in short the patch > > provides two different options to be compatible with Linux lockd > > implementations. It can also serve as a basis for a future more robust > > rpc.lockd. > > Thank you for this. I looked at this around 8 months ago but abandoned > further work on it because the approach I was taking required that > nfs be refactored to use the nmount() API, and because I am not currently > using NFS. It looks as though the two options implemented here helps to > address the problems I was having with making sure Linux servers got > the right lock cookie response. > > Have you tested this in production and does it work well? If so I believe > it should be committed, but I'd defer to Alfred for further review. It looks non0invasive enough to be safe. Please see if you can get a test run and commit it. I'm in the hospital and not able to do stuff. -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684