Mail Archives: cygwin/2002/07/24/15:14:21
* Jason Tishler <jason AT tishler DOT net> [24-07-02 14:37]:
> Jens,
>
> On Mon, Jul 22, 2002 at 10:20:49PM +0200, Jens Schuessler wrote:
> > I've compiled Mutt now with --enable-dotlock=NO
>
> IMO, the above is a bad idea because you are defeating one of the
> standard ways to lock a file to prevent corruption if there are multiple
> writers (e.g., mutt and procmail).
>
> While installing Cygwin exim yesterday, I *may* have stumbled onto your
> problem. After changing the permissions of /var/spool/mail to meet the
> needs of exim, I started to get the read-only mbox problem myself. I
> determined that if mutt cannot dotlock an mbox then it will open it
> read-only. This can easily tested by using mutt_dotlock:
>
> $ mutt_dotlock -t /var/spool/mail/jt
> $ echo $?
> 5
>
> Please try running mutt_dotlock -t on your mbox. Does it indicate
> incorrect permissions?
Hi Jason,
i would if i could, but there isn't a mutt_dotlock.exe in my
installation or in the official package!? I got a manpage for it, but
no executable. Normally, it should be a part of the mutt-package, or
am i wrong?
Jens
--
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/
- Raw text -