[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: pop3d and imap4d's locking behaviour
From: |
Alain Magloire |
Subject: |
Re: pop3d and imap4d's locking behaviour |
Date: |
Sat, 2 Mar 2002 16:34:53 -0500 (EST) |
>
> 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.
> IMAP's SELECT doesn't check mailbox return values either,
> this seems to work (in that select now fails if the mailbox
> can't be locked), but it modifies global state so I don't
> want to apply it, and there are other callers of this
> function that should likely check its status.
I do not remember the code so can not comment intelligently
about that piece.
> But its late and I have to go to bed.
>
Later.
- pop3d and imap4d's locking behaviour, Sam Roberts, 2002/03/01
- Re: pop3d and imap4d's locking behaviour, Sam Roberts, 2002/03/01
- Re: pop3d and imap4d's locking behaviour, Sam Roberts, 2002/03/02
- Re: pop3d and imap4d's locking behaviour,
Alain Magloire <=
- Re: pop3d and imap4d's locking behaviour, Sam Roberts, 2002/03/02
- Re: pop3d and imap4d's locking behaviour, Alain Magloire, 2002/03/02
- Message not available
- Re: pop3d and imap4d's locking behaviour, Sam Roberts, 2002/03/03
- Re: pop3d and imap4d's locking behaviour, Alain Magloire, 2002/03/03
- Message not available
- Re: pop3d and imap4d's locking behaviour, Sam Roberts, 2002/03/04
- Re: pop3d and imap4d's locking behaviour, Alain Magloire, 2002/03/05