From owner-freebsd-hackers Sun Mar 25 21:35:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id C305837B71A for ; Sun, 25 Mar 2001 21:35:24 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.11.3/8.11.3) id f2Q5ZMm24198; Sun, 25 Mar 2001 23:35:22 -0600 (CST) (envelope-from dan) Date: Sun, 25 Mar 2001 23:35:22 -0600 From: Dan Nelson To: Marc W Cc: FreeBSD Hackers Subject: Re: Locking and Mail spool Files Message-ID: <20010325233522.B1635@dan.emsphone.com> References: <200103260312.TAA31832@akira.lanfear.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.14i In-Reply-To: <200103260312.TAA31832@akira.lanfear.com>; from "Marc W" on Sun Mar 25 19:12:58 GMT 2001 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 25), Marc W said: > 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 ... ? As long as everything that touches your mailboxes use dotlocking, you should be safe. Use procmail as your local mailer, and make sure your mailreaders use dotlocking. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message