Re: reaching incoming connections queued max, what happens?

On Fri, 28 Sep 2007 13:01:23 -0400, Micah Anderson wrote:

> This leads me to wonder what would happen if I hit my SOMAXCONN with
> incoming messages, would they not be queued up? The SOMAXCONN on my
> linux box appears to be 128. So to test, I did the following on my spamd
> server, and then restarted spamd:
>
> echo "5" > /proc/sys/net/core/somaxconn
>
> I then issued 15 simultaneous connections with the -t value set to 15.
> Each individual connection took one second longer than the previous, as
> before, and those connections that took over the -t value were returned
> unscanned, as before. What puzzles me however is the fact that all of
> the connections acted just as before, when the SOMAXCONN was set to 128.
> Since each connection is coming in at exactly the same time I would
> expect that the first one would get accepted by spamd, 5 connections
> would be queued up, and then the 6+ connections would not be queued up
> and something would happen, but it doesn't, its the same as before...
> odd.

Well I'll be...

http://www.nntp.perl.org/group/perl.perl5.porters/2007/08/msg127373.html is a bug report that indicates that Socket::SOMAXCONN() seems to always return 128 on Linux, even though the value is dynamic and can be set and queried via /proc/sys/net/core/somaxconn.

Micah Received on Fri Sep 28 15:34:16 2007