Re: FAT32, "lock count exceeded", mutt etc.

2002-11-13 Thread Scott W Brim
On Wed, Nov 13, 2002 03:23:46PM -0500, Harig, Mark A. allegedly wrote: > If it is an option, you might consider > running the Windows 'convert' utility > to change your filesystem from FAT32 > to NTFS. Your operating system (Win2K) > support NTFS, of course. Thanks, but this is also the partition

RE: FAT32, "lock count exceeded", mutt etc.

2002-11-13 Thread Harig, Mark A.
mber 12, 2002 12:11 PM > To: [EMAIL PROTECTED] > Subject: FAT32, "lock count exceeded", mutt etc. > > > 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 >

Re: FAT32, "lock count exceeded", mutt etc.

2002-11-13 Thread Scott W Brim
My mistake, I wasn't using the patched version (/usr/bin versus /usr/local/bin). The patch seems to work. Thanks. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ:

Re: FAT32, "lock count exceeded", mutt etc.

2002-11-13 Thread Scott W Brim
On Tue, Nov 12, 2002 09:24:14PM -0500, Pierre A. Humblet allegedly wrote: > 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

Re: FAT32, "lock count exceeded", mutt etc.

2002-11-12 Thread Pierre A. Humblet
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

FAT32, "lock count exceeded", mutt etc.

2002-11-12 Thread Scott W Brim
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