From owner-freebsd-questions Thu Dec 19 17:34:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA26678 for questions-outgoing; Thu, 19 Dec 1996 17:34:33 -0800 (PST) Received: from edison.ebicom.net (ttsai@Edison.EbiCom.net [205.218.114.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA26669 for ; Thu, 19 Dec 1996 17:34:30 -0800 (PST) Received: (from ttsai@localhost) by edison.ebicom.net From: Tim Tsai Message-Id: <199612200134.TAA13044@edison.ebicom.net> Subject: Re: Freebsd for mail/shell server To: af@biomath.jussieu.fr (Alain FAUCONNET) Date: Thu, 19 Dec 1996 19:34:14 -0600 (CST) Cc: ttsai@pobox.com, questions@freebsd.org In-Reply-To: <199612191326.AA03396@iaka.biomath.jussieu.fr> from "Alain FAUCONNET" at Dec 19, 96 02:26:41 pm Receipt-To: ttsai@pobox.com Reply-To: ttsai@pobox.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > My rule is to use *only* mail user agents and mail delivery agents > that use and understand the most basic locking mechanism: dot file > locking i.e. creation of a /var/spool/mail/joe.lock file when > /var/spool/mail/joe is being accessed. Most mail user agents support > that, including elm if compiled with the proper options. Ah, thanks for the information. I was thinking too much. :-( I was worried about more advanced locking issues when mail doesn't use or need it. Tim