On Fri, 22 May 2009 02:46:21 +0000 (UTC)
J <b-sub-3eaf...@rope.net> wrote:
[...prefork...]
> However, I'm back to seeing the connection processes being left behind,
> despite an explicit quit from the remote host. I suspect this is due to
> not using a queueing plugin, at this point.
Err, maybe that's just because the name ($0) is not reset when the
connection ends? Prefork always keeps a number of processes around
(hence the name :))
[somehwere I had a patch which sets $0 of the master to
"qpsmtpd-prefork master" and all idle children to "qpsmtpd-prefork
idle"] 
Or do they accumulate, i.e. after every new connection there's a new
process? 

        Hanno

Reply via email to