Date: Fri, 13 Apr 2001 15:24:35 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Jonathan Lemon <jlemon@flugsvamp.com> Cc: tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: SOMAXCONN -- not tunable? Message-ID: <Pine.BSF.4.21.0104131501390.13944-100000@besplex.bde.org> In-Reply-To: <200104130008.f3D08nM61301@prism.flugsvamp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 Apr 2001, Jonathan Lemon wrote: > In article <local.mail.freebsd-current/200104111854.LAA25459@usr07.primenet.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0104131501390.13944-100000>