*BSD News Article 71601


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!inquo!news.uoregon.edu!news-res.gsl.net!news.gsl.net!news.mathworks.com!newsfeed.internetmci.com!news1.erols.com!newsmaster@erols.com
From: Ken Bigelow <kbigelow@www.play-hookey.com>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: File: Table is full?
Date: Thu, 20 Jun 1996 21:04:57 -0700
Organization: Erols Internet Services
Lines: 31
Message-ID: <31CA1F69.114B@www.play-hookey.com>
References: <4qcovc$23n@news2.inlink.com>
NNTP-Posting-Host: kenjb05.play-hookey.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.02 (Win16; I)

James Bass wrote:
> 
> Hello!  I am kinda new to freebsd, and I have a question...
> I am running a web server, and it is apache.  I run it from inetd.  I
> have a p-133 w/32Megs of ram...  okay!  everytime i look at dmesg or
> the error logs, it says httpd pid xxx uid 0 exited on signal 11
> kernel: File: table is full!  Okay, I recompiled the kernel before,
> using the Generic one and removing everything I didnt need.  ALSO I
> added the two oprions in the kernel for MAX_CHILD_whatever and set it
> at 200...  the MAX_FILES open or whatever i set to 200!  Actually I
> set them as high as 1000 once and no difference...  anyone have a
> clue???
> 

This may have to do with running it under inetd instead of standalone as 
FreeBSD and Apache are both set up to do. My server is running a 486DX-50 
with 32 MB RAM, and is happily running Apache 1.0.5 in standalone mode, 
with no trouble.

As I recall, the Apache docs specified some adjustments to the 
configuration to run under inetd; you may have trouble if you didn't make 
the changes. You may need to download the original package from 
http://www.apache.org and compile that after reconfiguring for inetd.

You may prefer to go back to standalone mode instead. It responds a 
little faster that way, and keeps a few child servers idle in case of 
simultaneous requests.

I hope this helps!

Ken