Date: Thu, 19 Jun 1997 06:31:42 -0400 (EDT) From: Jim Jagielski <jim@jaguNET.com> To: joe@pavilion.net (Josef Karthauser) Cc: questions@FreeBSD.ORG Subject: Re: SOMAXCONN, CHILD_MAX and OPEN_MAX Message-ID: <199706191031.GAA11201@devsys.jaguNET.com> In-Reply-To: <19970619101021.07770@pavilion.net> from "Josef Karthauser" at Jun 19, 97 10:10:21 am
next in thread | previous in thread | raw e-mail | index | archive | help
Josef Karthauser wrote:
>
> I'm still on this apache limit problem. :(
>
> A question that hopefully someone will know the answer to. The apache
> 1.2.0 FAQ has a section on tuning BSD derived kernels.
>
> It says that SOMAXCONN isn't derived from 'maxusers'. Is this true.
> They state that you can define it as a kernel option:
> options SOMAXCONN=512
> Is this true. I ask because it's also defined in socket.h. Do I need to
> tweak both values?
>
By setting the option in your kernel config file, you override the one
in socket.h. You'll get a load of warnings when building the new kernel
about SOMAXCONN being redefined, but that's OK. Ideally, the define
in socket.h should be #ifndef/#endif wrapped
--
====================================================================
Jim Jagielski | jaguNET Access Services
jim@jaguNET.com | http://www.jaguNET.com/
"Look at me! I'm wearing a cardboard belt!"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706191031.GAA11201>