Date: Sat, 16 Dec 2000 16:27:20 -0600 From: Dan Nelson <dnelson@emsphone.com> To: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>, Carsten Urbach <Carsten.Urbach@physik.fu-berlin.de> Cc: "David E. Cross" <crossd@cs.rpi.edu>, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? Message-ID: <20001216162720.A11561@dan.emsphone.com> In-Reply-To: <20001216164405.C9380@oberon.physik.fu-berlin.de>; from "Axel Thimm" on Sat Dec 16 16:44:05 GMT 2000 References: <Axel.Thimm@physik.fu-berlin.de> <200012142245.RAA69128@cs.rpi.edu> <20001216164405.C9380@oberon.physik.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Dec 16), Axel Thimm said: > Wouldn't that mean, that you might cause data corruption if, say, I > was to read my mail from a FreeBSD box over an NFS mounted spool > directory (running under OSF1 in our case), and I decided to write > back the mbox to the spool dir the same moment new mail is delivered? That's why dotlocking is recommended for locking mail spools. Both procmail and mutt will dotlock your mail file while it's being accessed. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001216162720.A11561>