[Dovecot] Return (revenge?) of the "pop-lock".
Hello,
The users here have been migrated to the new mail system with dovecot 0.99.10.5 (Debian package) on the backends. Storage is maildir, only pop3 access for now. I see very seldom occurrences (compared to the session wide pop lock of qpopper on the old system) like this:
Jun 16 14:35:52 mb01 pop3(user@gol.com): Timeout while waiting for release of exclusive fcntl() lock for index file /mail/spool/mb01/9ef/f73/af.user/.INBOX/.imap.index
These are people with slow connections and at least one large mail in the box, with their client aborting w/o terminating the session properly.
I presume the timeout for this is hardcoded, as all the config parameters for timeouts are mbox related, rite?
Regards,
Christian Balzer
Christian Balzer Network/Systems Engineer NOC chibi@gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/
On Wed, 2004-06-16 at 08:48, Christian Balzer wrote:
I see very seldom occurrences (compared to the session wide pop lock of qpopper on the old system) like this:
Jun 16 14:35:52 mb01 pop3(user@gol.com): Timeout while waiting for release of exclusive fcntl() lock for index file /mail/spool/mb01/9ef/f73/af.user/.INBOX/.imap.index
These are people with slow connections and at least one large mail in the box, with their client aborting w/o terminating the session properly.
I presume the timeout for this is hardcoded, as all the config parameters for timeouts are mbox related, rite?
Right. That's one annoying thing with 0.99.10 index code, slow readers will block others from accessing the mailbox. There's not much you can do except disable indexes, which would lose cached message sizes and slow down POP3 a lot.
The default timeout it 5 minutes already I think, so I'm not sure if growing it would help much.
Timo wrote:
On Wed, 2004-06-16 at 08:48, Christian Balzer wrote: [exclusive fcntl() lock for index file ...]
Right. That's one annoying thing with 0.99.10 index code, slow readers will block others from accessing the mailbox. There's not much you can do except disable indexes, which would lose cached message sizes and slow down POP3 a lot.
Not worth the hit given the far smaller number of "victims" compared to the qpopper lock.
The default timeout it 5 minutes already I think, so I'm not sure if growing it would help much.
If anything I might configure it lower, since most clients will have given up waiting for a response from the server after 5 minutes anyway. ;)
Regards and thanks for the insight,
Christian Balzer
Christian Balzer Network/Systems Engineer NOC chibi@gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/
participants (2)
-
Christian Balzer
-
Timo Sirainen