From owner-freebsd-hackers Sun Mar 25 19:13: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from akira.lanfear.com (akira.lanfear.com [208.12.11.174]) by hub.freebsd.org (Postfix) with ESMTP id A7E7637B718 for ; Sun, 25 Mar 2001 19:12:58 -0800 (PST) (envelope-from mwlist@lanfear.com) Received: from sapporo.lanfear.com (h-64-105-36-216.snvacaid.covad.net [64.105.36.216]) by akira.lanfear.com (8.9.3/8.9.3) with SMTP id TAA31832 for freebsd-hackers@freebsd.org; Sun, 25 Mar 2001 19:12:58 -0800 (PST) (envelope-from mwlist@lanfear.com) Date: Sun, 25 Mar 2001 19:12:58 -0800 (PST) From: Marc W Message-Id: <200103260312.TAA31832@akira.lanfear.com> To: "FreeBSD Hackers" Subject: Locking and Mail spool Files MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Mailer: Kiltdown 0.7 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 ... ? Thanks! marc. Marc W, San Francisco, CA Kiltdown -- a free email client for X www.kiltdown.org -- it's what's underneath that counts. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message