From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 05:02:19 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9251C37B404 for ; Sun, 22 Jun 2003 05:02:19 -0700 (PDT) Received: from frontend2.aha.ru (bird.zenon.net [213.189.198.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93D8043F3F for ; Sun, 22 Jun 2003 05:02:18 -0700 (PDT) (envelope-from uitm@blackflag.ru) Received: from [195.2.90.70] (HELO slt.oz) by frontend2.aha.ru (CommuniGate Pro SMTP 4.0.6) with ESMTP id 193883725; Sun, 22 Jun 2003 16:02:16 +0400 Received: (from uitm@localhost) by slt.oz (8.8.8/8.8.8) id QAA00842; Sun, 22 Jun 2003 16:04:00 +0400 (MSD) From: Andrey Alekseyev Message-Id: <200306221204.QAA00842@slt.oz> In-Reply-To: <20030622111457.GA51465@starfleet.org.au> from Rudolph Pereira at "Jun 22, 3 09:14:57 pm" To: memetical@yahoo.com.au (Rudolph Pereira) Date: Sun, 22 Jun 2003 16:03:58 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: nfs locking between current and stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2003 12:02:20 -0000 Rudolph, > I am attempting to get flock/file locking working between my -stable > (updated ~19 may) nfs file server and -current desktop; the server is > running lockd/statd, and both my mail client (mutt) and a simple perl > program complain that files on the nfs server cannot be locked. NFS locking wasn't implemented in 4.4BSD. There is still no implementation in STABLE. If you really need it, you may take a look at Terry's page where an intra-client NFS lock implementation for STABLE could be found: http://people.freebsd.org/~terry/ If you need the above mentioned patches that apply cleanly to RELENG_4, take a look at this: http://www.blackflag.ru/patches/nfs-client-and-server-locking-4.5-STABLE-20020312.diff It works fine in our production environment and was tested under quite a heavy load. However, do not miss that this patch doesn't actually implement lock requests to the server. It only allows for locks being properly held within a single client. That is, locks for the same file on several different STABLE boxes *won't* work. Thus, the word "intra-client" :) Hope this helps.