On Wed, 2007-05-16 at 14:17 +0200, Ralf Hildebrandt wrote:
- Timo Sirainen <tss@iki.fi>:
No. It means that it disconnected a client that wasn't yet logged in because login_max_connections was reached. It should happen only if login_max_processes_count was reached. Perhaps there's still a bug somewhere in there.. How many imap-login processes do you have running? Increasing login_processes_count probably helps for now.
root@postamt:~# ps auxwww |grep "imap \[" |wc -l 616 root@postamt:~# ps auxwww |grep "imap-login" |wc -l 14
So I have 616 "imap" processes and 14 imap-login processes. Each of the 14 handles up to 32 auth requests. And if I get this right, NEW imap-login processes are spawned automatically when the need arises. Correct?
That's correct, but if you're getting those kind of errors I guess there are some bugs. Are all those imap connections using SSL/TLS?
So I'm well below my limit of 128 imap-login processes. Or do I have to count other *-login processes as well?
The limits are counted separately for imap-logins and pop3-logins.