Re: pop3d and imap4d's locking behaviour

[Alain Magloire]

> 
> Quoting Alain Magloire <address@hidden>, who wrote:
> > > 
> > > Ok, 1 bug in mbx_mboxscan.c (wasn't checking return value
> > > of locker_lock()) fixed.
> > 
> > hum .. hum .. this was actually my doing.  I remember now
> > when testing the mailbox stuff, I was getting tired to always
> > "su -" and chmod to sgid on every recompile ... and forgot
> > about it.
> 
> :-) It happens!
> 
> I'm thinking about adding a MU_LOCKER_NO_LOCK mode, which will
> silently NOT lock the mailbox, so you can get that mode if you
> want. This would allow utilities that are opening mailboxes read
> only and just want to be fast (like "messages") to set this
> as a flag.

In theory it should not be necessary utils
like messages/frm/from should open the mailbox readonly
and never access write functions that could potentially locker_t
But it would still be nice on the safe side to MU_LOCKER_NO_LOCK
and maybe handy for something else.

> Also, I want to add a MU_LOCKER_EXTERNAL flag (and a
> locker_set_external(debug_t d, const char* program)) to call
> dotlock (or mutt_dotlock, if you'd rather). I think this would
> address the setgid irritation.

Yep!  This was forever on my TODO list.

> As soon as I can...

Cool!

> 
> Sam
> p.s. Spring is coming fast, a good thing.

8-) Ho! yes.