On 17 Jun 2005, at 00:35, Joe Schaefer wrote:
[EMAIL PROTECTED] (Justin Erenkrantz) writes:
On Thu, Jun 16, 2005 at 11:28:43AM -0400, Matt Sergeant wrote:
On 15 Jun 2005, at 14:47, Justin Erenkrantz wrote:
As I've mentioned before, we (apache.org) are seeing our qpsmtpd
processes stuck in an infinite loop. We're using
qpsmtpd-forkserver.
Do you have apache-2/mod_perl 2.x on that box? Sounds like you're
having problems with the server handling code and this would be a
good
opportunity to use Apache::Qpsmtpd - let it do all the connection
handling.
I was talking to Joe Schaefer and he said that the Apache::Qpsmtpd
code still had a bunch of bucket leaks and that we shouldn't use it.
I have no desire for us to be a guinea pig for untested code. --
justin
Me neither. Here's a patch that plugs the bucket leak and upgrades
Apache::Qpsmtpd to the mp2.0 API. I don't know what this module will
do under load, but it might be worth a shot if qpsmtpd-forkserver is
still segfaulting.
It's worth noting that the version of Apache/Qpsmtpd.pm you have is
also broken compared to the CVS one. I've applied this patch fixed up
against CVS now.
Matt.
