From owner-freebsd-current  Thu May 15 11:02:32 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA04221
          for current-outgoing; Thu, 15 May 1997 11:02:32 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA04208
          for <current@FreeBSD.ORG>; Thu, 15 May 1997 11:02:26 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA15223; Thu, 15 May 1997 10:54:49 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199705151754.KAA15223@phaeton.artisoft.com>
Subject: Re: RELENG_2_2
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Thu, 15 May 1997 10:54:49 -0700 (MST)
Cc: davidn@labs.usn.blaze.net.au, current@FreeBSD.ORG
In-Reply-To: <17811.863652120@time.cdrom.com> from "Jordan K. Hubbard" at May 14, 97 04:22:00 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > This is the real problem. Like many, I've been bitten by this
> > when simply accessing a mailbox via nfs. It won't happen often,
> > but it surely will.
> 
> Anyone who accesses a mailbox via NFS is living on the ragged
> edge anyway. ;-)

Not if (1) you have working locking and (2) you use that locking
in your mail programs and (3) NFS does not fail to meet its
specification required commitment to not return a write request
until the data has been committed to disk (ie: don't use SVR4
NFS, or if you do, modify the kernel variables controlling write
gathering on the client and async write on the server to disable
them so that the NFS servers become RFC compliant).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.