From owner-freebsd-isp Wed Jul 23 18:57:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA29740 for isp-outgoing; Wed, 23 Jul 1997 18:57:47 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA29726; Wed, 23 Jul 1997 18:57:36 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id TAA28356; Wed, 23 Jul 1997 19:55:01 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id TAA00673; Wed, 23 Jul 1997 19:55:38 -0600 (MDT) Date: Wed, 23 Jul 1997 19:55:37 -0600 (MDT) From: Marc Slemko Reply-To: Marc Slemko To: Aaron Jackson cc: gpalmer@FreeBSD.ORG, nevin@deepwell.com, freebsd-isp@FreeBSD.ORG Subject: Re: Limits on apache In-Reply-To: <9707232136.AA01622@negril.msrce.howard.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 23 Jul 1997, Aaron Jackson wrote: > The apache group released an update that addresses this problem. The > current release of apache is 1.2.1. There should also be a workaround > posted on the faq at www.apache.org. I hope this helps. Yes. If you use 1.2.1 on FreeBSD 2.2.x, it should work fine as long as you set the right ulimits (if necessary, run a ulimit -n unlimited in a shell script that starts Apache) and compile Apache (just Apache, you don't need to recompile everything else) with -DFD_SETSIZE=1024 or some similar number. You shouldn't need to tune the Apache "slack" settings at all. Apache does try to magically increase the limit on file descriptors (adds 2 per virtual host), but that isn't always possible. With 1.2.0, that won't work a lot of the time because BIND has broken code that sets a hard limit based on the FD_SETSIZE setting when BIND was compiled. You would have to recompile the resolver library with a larger FD_SETSIZE to fix that on 1.2.0. However, as Gary says, this is a limit on the number of file descriptors not interfaces. However, you do _not_ need one descriptor per interface. You need one descriptor per logfile, one descriptor per Listen directive, and a couple more on the top for various things. If you have a lot of virtual hosts it is best if you can avoid using Listen directives because they add overhead. > > Aaron Jackson jackson@msrce.howard.edu > > >> I am running a web server using apache 1.2 and stronghold 3.0 both > >> on freebsd 2.2.2. > > > >> It seems the the server wants to go boom if I try to bind more than > >> 150 ip addresses to the network interface with ifconfig. > > > >> Has anyone else had this problem or might know if there is a limit > >> to the number of ip addesses that can be used? > > > >No, the limit is on the number of file descriptors you can have open > >from one process. I bet once you add up the number of file descriptors > >(i.e. 1 per IP address, one per log file you have defined in apache) > >that you will run into the per-process limit that is defined on your > >machine. Try using the apache 1.2 commands (sorry, I don't have the > >docs avail right now) to increase the resource limits, specifically > >the number of file descriptors, and see if that helps. >