Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Mutt 1.4-1 opens mbox read-only
References: <20020722202048 DOT GA21538 AT trash DOT net>
	<20020724123728 DOT GA1556 AT tishler DOT net>
X-Face: I-*}xvwusAv%MlABo'jVNP7TDXf5bb*L[q,r{DnsR1GoL07^Wf)sAu%>!LjXAFlZZN+`OQu
	}?#du]C)[*%ERKR#+l#sX'EoNbSO~|.x AT ogoS5|"-u?<s5ViLslvYMlj7_n!Tq1m AT xt2Bhj4[Zg+e?
	/Yy\SE`V?%v~kRU3GoS1f&U]}
From: "Dr. Volker Zell" <Dr DOT Volker DOT Zell AT oracle DOT com>
Date: Wed, 24 Jul 2002 21:20:03 +0200
In-Reply-To: <20020724123728.GA1556@tishler.net> (Jason Tishler's message of
 "Wed, 24 Jul 2002 08:37:28 -0400")
Message-ID: <87znwhszks.fsf@vzell-de.de.oracle.com>
Lines: 33
User-Agent: Gnus/5.090005 (Oort Gnus v0.05) XEmacs/21.4 (Common Lisp
 (candidate 1), i686-pc-cygwin)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

>>>>> "Jason" == Jason Tishler <jason AT tishler DOT net> writes:

    Jason> Jens,
    Jason> On Mon, Jul 22, 2002 at 10:20:49PM +0200, Jens Schuessler wrote:
    >> I've compiled Mutt now with --enable-dotlock=NO

    Jason> IMO, the above is a bad idea because you are defeating one of the
    Jason> standard ways to lock a file to prevent corruption if there are multiple
    Jason> writers (e.g., mutt and procmail).

    Jason> While installing Cygwin exim yesterday, I *may* have stumbled onto your
    Jason> problem.  After changing the permissions of /var/spool/mail to meet the
    Jason> needs of exim, I started to get the read-only mbox problem myself.  I
    Jason> determined that if mutt cannot dotlock an mbox then it will open it
    Jason> read-only.  This can easily tested by using mutt_dotlock:

    Jason>     $ mutt_dotlock -t /var/spool/mail/jt
    Jason>     $ echo $?
    Jason>     5

    Jason> If you get a "5" (instead of "0"), then the permissions of
    Jason> /var/spool/mail are not correct.

    Jason> Please try running mutt_dotlock -t on your mbox.  Does it indicate
    Jason> incorrect permissions?

Where is mutt_dotlock ? There is only a usr/man/man1/mutt_dotlock.1 in
mutt-1.4-1.tar.bz2.

    Jason> Jason

Ciao
  Volker


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/