From owner-freebsd-questions Thu Jun 19 03:32:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20960 for questions-outgoing; Thu, 19 Jun 1997 03:32:04 -0700 (PDT) Received: from devsys.jaguNET.com (devsys.jaguNET.com [206.156.208.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20953 for ; Thu, 19 Jun 1997 03:32:02 -0700 (PDT) Received: (from jim@localhost) by devsys.jaguNET.com (8.8.5/jag-2.4) id GAA11201; Thu, 19 Jun 1997 06:31:43 -0400 (EDT) From: Jim Jagielski Message-Id: <199706191031.GAA11201@devsys.jaguNET.com> Subject: Re: SOMAXCONN, CHILD_MAX and OPEN_MAX To: joe@pavilion.net (Josef Karthauser) Date: Thu, 19 Jun 1997 06:31:42 -0400 (EDT) Cc: questions@FreeBSD.ORG Reply-To: jim@jaguNET.com In-Reply-To: <19970619101021.07770@pavilion.net> from "Josef Karthauser" at Jun 19, 97 10:10:21 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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!"