>Yes, 700 connections seems high, but after some period of down time, it seems to
Just to emphasize what I was saying. I reckon for 30K users (was that the
number-ish?), 700 is far higher than normal. I know there is no such thing
as normal, but...
> tcpserver -l$hostvalue -q -b100 -H -R -D 0 pop-3
> tcpserver -l$hostvalue -q -b50 -H -R -D 0 2001
> tcpserver -l$hostvalue -t8 -q -b5000 -D -u502 -g2108
> tcpserver -l$hostvalue -t8 -q -b50 -D -u502 -g2108
In all cases, change the -b to a -c
>After reading "man listen" I am reminded of the help this list gave us when we
>had this problem before. Our connections were being artificially limited by
>Linux to 5 at a time! This was solved with adding the -b20 (then later upping
It *may* be worth upping it beyond the default, but the listen queue really
only comes into effect if tcpserver isn't keeping up with the inbound
connection rate.
As long as tcpserver is doing the accept and passoff to qmail-smtpd in
enough time, the backlog doesn't apply. the concurrency with -c does of course.
>If one server reaches this limit, it is overloaded and if lucky it is dropped
>out of the rotation by the alteon. This causes the other servers to overload
>and reach the same state.
Is the alteon configured to load balance of switch on no response?
Also, is it possible to bypass the Alteon for a while? There may be some
unknown interaction there.
Regards.
