From owner-freebsd-current Thu Apr 12 22:25:40 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 5A8BA37B424 for ; Thu, 12 Apr 2001 22:25:37 -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 PAA00180; Fri, 13 Apr 2001 15:25:27 +1000 Date: Fri, 13 Apr 2001 15:24:35 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jonathan Lemon Cc: tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: SOMAXCONN -- not tunable? In-Reply-To: <200104130008.f3D08nM61301@prism.flugsvamp.com> 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 Thu, 12 Apr 2001, Jonathan Lemon wrote: > In article you write: > >Here are patches to make SOMAXCONN tunable from the config files. > > > >Right now, it's not possible to override SOMAXCONN. > > sysctl -w kern.ipc.somxconn=1024 > > SOMAXCONN is just a compile time default, and yes it is not > currently tunable at config time. Does it really have to be? Of course it doesn't have to be tunable at config time. > Just stick it in /etc/sysctl.conf, and it gets set before most > things are started in the system. 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message