This is the mail archive of the
mailing list for the Cygwin project.
Re: mutt/procmail lock problem
On Mon, Dec 17, 2001 at 11:50:03PM -0600, Gary R. Van Sickle wrote:
> From: Jason Tishler [mailto:firstname.lastname@example.org]
> > 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
> 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
Anyway, just replace:
#define USE_DOTLOCK 1
> > 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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html