From owner-freebsd-current Fri Apr 13 4:29:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 52E8937B423 for ; Fri, 13 Apr 2001 04:29:14 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA18421; Fri, 13 Apr 2001 21:29:02 +1000 Date: Fri, 13 Apr 2001 21:28:06 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alfred Perlstein Cc: Jonathan Lemon , tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: SOMAXCONN -- not tunable? In-Reply-To: <20010413040125.E976@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Apr 2001, Alfred Perlstein wrote: > * Bruce Evans [010412 22:25] wrote: > > Changing the actual limit using either the sysctl or an option breaks > > SOMAXCONN. I think the correct fix is to never define it change > > whatever uses it to use sysconf(_SC_SOMAXCONN). Similarly for all > > other manifest constants that aren't actually constant. > > Actually, the correct fix is most likely to redefine it to -1. :) > > Either that or remove it from the namespace. Or just leave it alone, > afaik listen called with a backlog larger than the sysctl limit > just truncates it down to that limit. Or change it to a large positive value, maybe INT_MAX, and prevent the sysctl from increasing it above this. This would be reduced to the actual limit in the same way as -1 is modified to that limit, but might seem to be less preposterous to applications that look too closely at the value. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message