I might be stuck in apache 1.x land, but isn't that what MaxClients
and the like are for? The server status page should give you the info
you need about number of active connections. For example, on my
straight up HTTP apache2 server, I have this in apache2.conf:
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 20
MaxRequestsPerChild 0
</IfModule>
HTH.
Cheers,
Brian
On Oct 5, 2006, at 12:32 PM, Peter Eisch wrote:
In my instances I couldn't figure out the right number for limiting
connections. It got problematic when roadwarrior SMTP AUTH users were
unable to connect reliably.
Is the specific problem you're looking to solve simply connection
limits or
is there a different situation that you want connection limits to
solve? If
may anticipate the answer as being the latter.... I keep the
system from
drowning from massive waves by using the loadcheck plugin. They
can then
take the plethora of connections but when spamd starts sucking cpu to
service the connected MTAs, it will just fire back a soft error.
I've had
very good experiences from this approach as well as when I was
running the
tcpserver framework.
If you are specifically looking to limit connections, I'm sorry but
I have
no solution.
peter
---
Brian Szymanski
[EMAIL PROTECTED]
