This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Mutt 1.4-1 opens mbox read-only


>>>>> "Jason" == Jason Tishler <jason@tishler.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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]