2 Jul
2007
2 Jul
'07
9:58 a.m.
On Mon, 2 Jul 2007 15:20:14 +0900 Christian Balzer <chibi@gol.com> wrote:
Of course now it looks like this is not LDAP related after all.
Well, lemme rephrase that. It looks like the LDAP connection pool is not the culprit.
I just re-ran the test with local users (shadow as passdb and passwd as userdb) and while the dovecot-auth process does NOT grow the pool output is identical to the LDAP runs after the same time:
Jul 2 15:52:15 engtest03 dovecot: auth(default): pool auth request handler: 104 / 4080 bytes Jul 2 15:52:15 engtest03 last message repeated 137 times Jul 2 15:52:15 engtest03 dovecot: auth(default): pool passwd_file: 56 / 10224 bytes Jul 2 15:52:15 engtest03 dovecot: auth(default): pool Environment: 224 / 2032 bytes Jul 2 15:52:15 engtest03 dovecot: auth(default): pool auth: 1432 / 2032 bytes
So I guess back to square one, as in the leak is not happening in the pools (or at least it's not visible here), but it clearly seems to happen (just?) with LDAP.
Regards,
Christian
Christian Balzer Network/Systems Engineer NOC chibi@gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/