[Dovecot] Login processes don't die
Hello,
I'm a fresh dovecot user (resp. admin), using dovecot 0.99.14 (a little old, but that's what Debian Sarge provides). In general everything works as it should, but there's something that makes me wonder.
The wiki says "By default each login process will handle only a single connection and afterwards kill itself." But it does look different to me.
On startup there are two imap-login processes running (login_processes_count is 2). When connecting with Sylpheed, one additional imap process is running.
But when connecting with Mozilla (Seamonkey), I get three imap-login and one imap process at minimum (Maximum number of server connections to cache set to 1 in Mozilla). If the cached connections is set to 2, there are four imap-login and two imap processes.
So it looks to me as the login processes don't get killed. Is this a client issue (but how could it keep the login alive?), is this a known bug in the older dovecot, or something unknown?
BTW, login_process_per_connection is default.
Regards, Jürgen
On Fri, 2006-02-17 at 14:30 +0100, Jürgen Herz wrote:
The wiki says "By default each login process will handle only a single connection and afterwards kill itself." But it does look different to me.
It continues with "The login processes handle SSL/TLS connections themselves completely. They keep proxying the connection to mail processes for the entire lifetime of the connection."
I'll try to make it a bit clearer..
Timo Sirainen wrote:
On Fri, 2006-02-17 at 14:30 +0100, Jürgen Herz wrote:
The wiki says "By default each login process will handle only a single connection and afterwards kill itself." But it does look different to me.
It continues with "The login processes handle SSL/TLS connections themselves completely. They keep proxying the connection to mail processes for the entire lifetime of the connection."
Oh indeed, that's what "but see SSL proxying below" means. Thank you for the hint.
I'll try to make it a bit clearer..
Now I know how it's meant it's obvious, but it guess it could be written just more obvious.
Jürgen
P.S. This is the fourth try getting this message to the list since my previous ones don't show up after all in all 24 hours. So please ignore any dupes if the previous might finally show up.
On Friday 17 Feb 2006 13:30, Jürgen Herz wrote:
The wiki says "By default each login process will handle only a single connection and afterwards kill itself." But it does look different to me.
The login process parents the session and dies at the end of the session.
But when connecting with Mozilla (Seamonkey)
Seamonkey creates multiple sessions
So it looks to me as the login processes don't get killed. Is this a client issue (but how could it keep the login alive?), is this a known bug in the older dovecot, or something unknown?
I think it is working as designed.
I see three logins, connect via thunderbird create a fourth, when I kill thunderbird, one of the original three dies.
Some servers have issues with how Mozilla works with multiple connections, but I don't think it is an issue for dovecot, and really shouldn't be an issue for any IMAP server.
Simon Waters wrote:
But when connecting with Mozilla (Seamonkey)
Seamonkey creates multiple sessions
If connection caching is set to > 1, yes. But even with only one the login persisted when using Seamonkey and didn't when using Sylpheed. But now I know the reason was that Sylpheed connected without TLS ...
I see three logins, connect via thunderbird create a fourth, when I kill thunderbird, one of the original three dies.
Hm, I can do what I want, but one of the original ones (two here as configured) never dies. But that's what I expect since I guess that are the parents which spawn their childs on login.
Jürgen
participants (3)
-
Jürgen Herz
-
Simon Waters
-
Timo Sirainen