Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Tue, 12 Nov 2002 21:24:14 -0500 From: "Pierre A. Humblet" To: cygwin AT cygwin DOT com Subject: Re: FAT32, "lock count exceeded", mutt etc. Message-ID: <20021113022414.GA98225245@HPN5170X> References: <011c01c28a6e$712e2380$6401a8c0 AT amer DOT cisco DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <011c01c28a6e$712e2380$6401a8c0@amer.cisco.com> User-Agent: Mutt/1.4i On Tue, Nov 12, 2002 at 12:10:40PM -0500, Scott W Brim wrote: > Looking through the mail archives I can't tell what the recommended fix > is for running mutt/fetchmail/procmail and all on a FAT32 partition, wrt > file locking problems. There was plenty of discussion last summer but I > can't find a resolution. So far I've tried CYGWIN=nontsec, and > reconfiguring and recompiling mutt. No luck. Help? What are the magic > words? Mutt needs two fixes to run on FAT: - a fix to Cygwin, included since October. - a patch to mutt, see below. The mutt maintainer is aware of this patch. I hope it eventually will become part of the mutt distribution. It helps FAT without hurting anything. Pierre P.S.: this message was sent by mutt on WinME --- dotlock.c.orig 2002-09-17 22:37:46.000000000 -0400 +++ dotlock.c 2002-09-17 22:40:28.000000000 -0400 @@ -586,7 +586,7 @@ char lockfile[_POSIX_PATH_MAX + LONG_STRING]; char nfslockfile[_POSIX_PATH_MAX + LONG_STRING]; size_t prev_size = 0; - int fd; + int fd, res; int count = 0; int hard_count = 0; struct stat sb; @@ -625,9 +625,12 @@ { BEGIN_PRIVILEGED (); - link (nfslockfile, lockfile); + res = link (nfslockfile, lockfile); END_PRIVILEGED (); + if (!res) + break; + if (stat (nfslockfile, &sb) != 0) { /* perror ("stat"); */ -- 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/