From owner-freebsd-hackers Sun Mar 25 19:20:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 0E4B037B718 for ; Sun, 25 Mar 2001 19:20:35 -0800 (PST) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f2Q3JcY50055; Sun, 25 Mar 2001 19:19:38 -0800 (PST) Date: Sun, 25 Mar 2001 19:19:38 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Marc W Cc: FreeBSD Hackers Subject: Re: Locking and Mail spool Files In-Reply-To: <200103260312.TAA31832@akira.lanfear.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look for Alfred's commit of Mar 19th. There has been a *huge* overhaul of the nfs stuff and (I think) a working lockd. I haven't looked at it myself, so check it out for yourself. -gordon On Sun, 25 Mar 2001, Marc W wrote: > So, in a discussion a while back, it was established that file > locking is basically broken under NFS. Does this mean that it is > simply a REALLY BAD idea to put mail spool files on NFS mounts, or are > there ways that programs like /bin/mail can correctly ensure > consistency while reading in data ... ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message