Maximum backlog on "listen" calls

Article View: net.lan

Article #1089

#1089

From: Eric Bergan
Date: Tue, 13 May 1986 13:05

15 lines
1160 bytes

	We are developing a system that will be primarily dedicated to
servers for the network. Currently, the "listen" call limits the
size of the backlog queue to 5. This is done by a #define of SOMAXCONN.
I would be interested in knowing the relative pros and cons of increasing
SOMAXCONN, since this occasionally causes one of our clients to fail
to connect. In looking at the code, the only place SOMAXCONN is used is
in a "min" statement with the "backlog" parameter. Does anyone know
why 5 was chosen? Will we consume massive memory, or destroy our
network throughput if we reset it to, say 16?

-- 

					eric
					...!seismo!umcp-cs!aplcen!osiris!eric

Technical Details

Message-ID: <792@osiris.UUCP>

Path: arc1-ca.pugleaf.net!utzoo!linus!philabs!cmcl2!harvard!seismo!umcp-cs!aplcen!osiris!eric

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!linus!philabs!cmcl2!harvard!seismo!umcp-cs!aplcen!osiris!eric
From: eric@osiris.UUCP (Eric Bergan)
Newsgroups: net.lan,net.unix-wizards
Subject: Maximum backlog on "listen" calls
Message-ID: <792@osiris.UUCP>
Date: Tue, 13-May-86 09:05:03 EDT
Article-I.D.: osiris.792
Posted: Tue May 13 09:05:03 1986
Date-Received: Thu, 15-May-86 06:21:38 EDT
Distribution: net
Organization: Johns Hopkins Hospital
Lines: 15