Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Apr 2001 10:16:07 -0400 (EDT)
From:      Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To:        Alfred Perlstein <bright@wintelcom.net>
Cc:        current@FreeBSD.ORG
Subject:   Re: SOMAXCONN -- not tunable?
Message-ID:  <200104131416.KAA58869@khavrinen.lcs.mit.edu>
In-Reply-To: <20010413040125.E976@fw.wintelcom.net>
References:  <200104130008.f3D08nM61301@prism.flugsvamp.com> <Pine.BSF.4.21.0104131501390.13944-100000@besplex.bde.org> <20010413040125.E976@fw.wintelcom.net>

next in thread | previous in thread | raw e-mail | index | archive | help
<<On Fri, 13 Apr 2001 04:01:25 -0700, Alfred Perlstein <bright@wintelcom.net> said:

> Actually, the correct fix is most likely to redefine it to -1. :)

POSIX.1-200x draft 5 has this to say:

	Implementations shall support values of backlog up to
	SOMAXCONN, defined in <sys/socket.h>

	If listen( ) is called with a backlog argument value that is
	less than 0, the function behaves as if it had been called
	with a backlog argument value of 0.  A backlog argument of 0
	may allow the socket to accept connections, in which case the
	length of the listen queue may be set to an
	implementation-defined minimum value.

So, SOMAXCONN is supposed to be a minimum maximum.

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104131416.KAA58869>