From owner-freebsd-stable@FreeBSD.ORG  Thu Jan  6 08:50:41 2011
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 34023106564A;
	Thu,  6 Jan 2011 08:50:41 +0000 (UTC)
	(envelope-from perryh@pluto.rain.com)
Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34])
	by mx1.freebsd.org (Postfix) with ESMTP id 13F8B8FC15;
	Thu,  6 Jan 2011 08:50:41 +0000 (UTC)
Received: from agora.rdrop.com (66@localhost [127.0.0.1])
	by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p068obeM039490
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 6 Jan 2011 00:50:37 -0800 (PST)
	(envelope-from perryh@pluto.rain.com)
Received: (from uucp@localhost)
	by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p068obwg039489; 
	Thu, 6 Jan 2011 00:50:37 -0800 (PST)
Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407)
	id AA16538; Thu, 6 Jan 11 00:45:09 PST
Date: Thu, 06 Jan 2011 00:44:48 -0800
From: perryh@pluto.rain.com
To: rmacklem@uoguelph.ca
Message-Id: <4d258100.Wu9WZrgdH2/KvDTa%perryh@pluto.rain.com>
References: <1870282066.118978.1294234205820.JavaMail.root@erie.cs.uoguelph.ca>
In-Reply-To: <1870282066.118978.1294234205820.JavaMail.root@erie.cs.uoguelph.ca>
User-Agent: nail 11.25 7/29/05
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: marek_sal@wp.pl, freebsd-stable@freebsd.org, milu@dat.pl,
	jyavenard@gmail.com, jhb@freebsd.org
Subject: Re: NFSv4 - how to set up at FreeBSD 8.1 ?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2011 08:50:41 -0000

Rick Macklem <rmacklem@uoguelph.ca> wrote:

> Sun did add a separate file locking protocol called the NLM
> or rpc.lockd if you prefer, but that protocol design was
> fundamentally flawed imho and, as such, using it is in the
> "your mileage may vary" category.

I suppose it was not all that bad, considering that what it sought
to accomplish is incomputable.  There is simply no way for either
the server or the client to distinguish between "the other end has
crashed" and "there is a temporary communication failure" until the
other end comes back up or communication is restored.

On a good day, in a completely homogeneous environment (server and
all clients running the same OS revision and patchlevel), I trust
lockd about as far as I can throw 10GB of 1980's SMD disk drives :)

Exporting /var/spool/mail read/write tends to ensure that good days
will be rare.  Been there, done that, seen the result.  Never again.
That's what IMAP is for.