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
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 18 Dec 2001 07:07:37 -0500
From:	Jason Tishler <jason AT tishler DOT net>
To:	Cygwin <cygwin AT sources DOT redhat DOT com>
Subject:	Re: mutt/procmail lock problem
Message-ID:	<20011218120737.GA1420@dothill.com>
Mail-Followup-To:	Cygwin <cygwin AT sources DOT redhat DOT com>
References:	<20011217145234 DOT GA1640 AT dothill DOT com> <NCBBIHCHBLCMLBLOBONKGEPFCHAA DOT g DOT r DOT vansickle AT worldnet DOT att DOT net>
Mime-Version:	1.0
In-Reply-To:	<NCBBIHCHBLCMLBLOBONKGEPFCHAA.g.r.vansickle@worldnet.att.net>
User-Agent:	Mutt/1.3.24i

Gary,

On Mon, Dec 17, 2001 at 11:50:03PM -0600, Gary R. Van Sickle wrote:
> From: Jason Tishler [mailto:jason AT tishler DOT net]
> > I recommend "fixing" the permissions of "/var/spool/mail" on your machine:
> >
> >     $ chmod g+w /var/spool/mail
> 
> Done and done, and of course... it does nothing for me.  Either with
> ntsec or no ntsec, ls -l comes back exactly the same.  Dag nabbit.

Hmm...  The chmod should work at least with ntsec.  If you recently
enabled ntsec, then make sure to exit *all* Cygwin process before trying
again.

> Well at least I know what needs fixing now.  If I can't get the group
> permissions set right, perhaps I can force the configure somehow.

You can always edit config.h (after running configure) -- this is
what I did until I traced through configure.in and figured out the
group permission requirement.  Too bad there isn't a configure option
for this...

Anyway, just replace:

    #undef USE_DOTLOCK

with:

    #define USE_DOTLOCK 1

in config.h.

> > and then releasing a new mutt package.
> >
> 
> Or perhaps... two? ;-)

Why two?  One package with USE_DOTLOCK enabled will handle both cases
-- locking required and locking unnecessary.

> Thanks for the heads-up Jason, this is great info,
> especially since I don't use procmail currently and would otherwise probably
> never have caught this, let alone figured out what to do about it.

No problem.  It was just the standard situation -- I had the itch...

Thanks for being open to "fixing" your package.

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/

- Raw text -