Re: mutt/procmail lock problem

Re: mutt/procmail lock problem

[Gary R Van Sickle]

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

I've got the 1.3.24 "released beta" working better than 1.2.5i now (I got
binary sending and recieving and mboxes working regardless of mount type).
But keep it under your hat, we don't want to cause a stampede ;-).

--
Gary R. Van Sickle
Braemar Inc.
11481 Rupp Dr.
Burnsville, MN 55337


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

Re: mutt/procmail lock problem

[Jason Tishler]

Gary,

On Tue, Dec 18, 2001 at 12:41:07PM -0600, Gary R Van Sickle wrote:
> > > > and then releasing a new mutt package.
> > >
> > > Or perhaps... two? ;-)
> >
> > Why two?
> 
> I've got the 1.3.24 "released beta" working better than 1.2.5i now (I got
> binary sending and recieving and mboxes working regardless of mount type).
> But keep it under your hat, we don't want to cause a stampede ;-).

Ah, now I understand the reference.  This a good news!  I look forward
to your 1.3.x release, so I can pitch my private build and start using
the official one again...

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

Re: mutt/procmail lock problem

[Jason Tishler]

Gary,

On Mon, Dec 17, 2001 at 11:50:03PM -0600, Gary R. Van Sickle wrote:
> From: Jason Tishler [mailto:jason@tishler.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/

RE: mutt/procmail lock problem

[Gary R. Van Sickle]

From: Jason Tishler [mailto:jason@tishler.net]
> Gary,
>
> I just discovered a locking problem with mutt 1.3.x that I believe
> also affects the mutt 1.2.x that you contributed to Cygwin.  This lock
> problem caused procmail to misfile messages to the wrong mbox file when
> mutt happened to be writing to the mbox file that should have received
> the message.  Under this situation, procmail complains to its logfile
> with error messages of the following form:
>
>     Error while writing to "x"
>
> IMO, the root cause is due to "incorrect" group permissions for
> "/var/spool/mail" on the build machine:
>
>     $ ls -ld /var/spool/mail
>     drwxr-xr-x    2 jtishler Administ        0 Dec 17 09:06 /var/spool/mail
>          ^
>          +--- should be writable
>

Sure enough, it isn't here.  Good catch!

> When built on such a machine, mutt's configure does not enable dotlocking:
>
>     $ mutt -v
>     Mutt 1.2.5i (2000-07-28)
>     [snip]
>     System: CYGWIN_NT-5.0 1.3.6(0.47/3/2) [using ncurses 5.2]
>     Compile options:
>     -DOMAIN
>     -DEBUG
>     -HOMESPOOL  -USE_SETGID  -USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
>                              ^^^^^^^^^^^^
>
> 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.  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.

> and then releasing a new mutt package.
>

Or perhaps... two? ;-)  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.

--
Gary R. Van Sickle
Brewer.  Patriot.


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

mutt/procmail lock problem

[Jason Tishler]

Gary,

I just discovered a locking problem with mutt 1.3.x that I believe
also affects the mutt 1.2.x that you contributed to Cygwin.  This lock
problem caused procmail to misfile messages to the wrong mbox file when
mutt happened to be writing to the mbox file that should have received
the message.  Under this situation, procmail complains to its logfile
with error messages of the following form:

    Error while writing to "x"

IMO, the root cause is due to "incorrect" group permissions for
"/var/spool/mail" on the build machine:

    $ ls -ld /var/spool/mail
    drwxr-xr-x    2 jtishler Administ        0 Dec 17 09:06 /var/spool/mail
         ^
         +--- should be writable

When built on such a machine, mutt's configure does not enable dotlocking:

    $ mutt -v  
    Mutt 1.2.5i (2000-07-28)
    [snip]
    System: CYGWIN_NT-5.0 1.3.6(0.47/3/2) [using ncurses 5.2]
    Compile options:
    -DOMAIN
    -DEBUG
    -HOMESPOOL  -USE_SETGID  -USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
                             ^^^^^^^^^^^^

I recommend "fixing" the permissions of "/var/spool/mail" on your machine:

    $ chmod g+w /var/spool/mail

and then releasing a new mutt package.

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