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
Date: Fri, 22 Mar 2002 09:25:23 -0500
From: Jason Tishler <jason AT tishler DOT net>
Subject: procmail locking problem warning (was Re: procmail on cygwin)
In-reply-to: <20011210134958.A2088@dothill.com>
To: Cygwin <cygwin AT sources DOT redhat DOT com>
Mail-followup-to: Cygwin <cygwin AT sources DOT redhat DOT com>
Message-id: <20020322142523.GB2316@tishler.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.3.24i
References: <017101c181a0$b47a29e0$738ffe0c AT pwork>
 <20011210134958 DOT A2088 AT dothill DOT com>

On Mon, Dec 10, 2001 at 01:49:58PM -0500, Jason Tishler wrote:
> Otherwise, you can try my attached build recipe.

I found an issue with my procmail build recipe that causes a mbox file
locking problem.  So, I'm posting this warning.

If interested, see the following for the aforementioned recipe:

    http://sources.redhat.com/ml/cygwin/2001-12/msg00543.html

Occasionally, I would get errors such as the following in my procmail.log
file:

    procmail: Error while writing to "/var/spool/mail/jt"
    procmail: Truncated file to former size

The above is due to procmail's autoconf (script) adding the following
to autoconf.h:

    /*locktype: 4, countlocks: 80, timeout 0, watchdog 1a, /tmp/_locktest*/
    /*locktype: 2, countlocks: 80, timeout 0, watchdog 17, /tmp/_locktest*/
    /*locktype: 1, countlocks: 80, timeout 0, watchdog 1a, /tmp/_locktest*/
    /* Hotwire LOCKINGTEST=000 */
    /* Procmail will lock via: dotlocking */
    #define NOfcntl_lock

The specific culprit is the "#define NOfcntl_lock" which disables fcntl()
locking support in procmail.  Since, mutt uses fcntl() and dotlocking,
there is a small window in which a mbox file is locked via fcntl() but
not yet via dotlocking.  This is the root cause to my transient procmail
write errors.

My WAG is that procmail's autoconf is having problems with missing
".exe" strings in executable names during mv operations:

    Initiating fcntl()/kernel-locking-support tests
    mv: preserving times for `_locktst': No such file or directory
    mv: preserving ownership for `_locktst': No such file or directory
    mv: cannot unlink `_autotst': No such file or directory
    mv: cannot remove `_autotst': No such file or directory

I have temporarily "fixed" the problem by commented out the "#define
NOfcntl_lock" in autoconf.h while I wade through the obfuscated procmail
coding style.

Maybe it's time for maildrop... :,)

Jason

--
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/