Re: Pernicious problem with vfork / qmail / qmail-scanner (RESOLVED)

[Justin Baugh, KSC]

Happen to catch this, this morning... Good dig on this..

Tcpserver *defaults* to a maximum of 40 simultaneous connections, so 
this could very well be where your problem is.. Sorry, should have 
thought of this earlier.

You can raise this limit with the -c n (n=number) option..

Please see


Nope, I'm aware of that limit, and -c was set to 120. The problem
would arise with any number for n...no matter what, it would still get
caught up at 40 connections.
The fact that I couldn't replicate the problem with the exact same setup
under 5.2.1R makes me think it's something related to the version that
came with the machine.
Thanks,

-Justin

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Pernicious problem with vfork / qmail / qmail-scanner (RESOLVED)

[Gary]

Hi Justin,

--On Sunday, March 14, 2004 11:37:13 AM -0500 "Justin Baugh, KSC" 
<[EMAIL PROTECTED]> wrote:

So, after much testing & debugging:

* The problem only happens with tcpserver
* The problem is not replicable in any way under 5.2.1R
* The problem happens with any service/user with tcpserver, not just
   qmail-smtpd/qmaild
I set up a testbed on my home box with a vanilla qmail install, and I
wasn't able to get it to choke up. As a workaround (until I can upgrade
the other box to 5.2.1R) I am running qmail through xinetd /
tcpwrappers (heresy, I know), and all is well.
Happen to catch this, this morning... Good dig on this..

Tcpserver *defaults* to a maximum of 40 simultaneous connections, so this 
could very well be where your problem is.. Sorry, should have thought of 
this earlier.

You can raise this limit with the -c n (n=number) option..

Please see



--
Gary
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"