You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Marc Slemko <ma...@znep.com> on 1997/04/27 21:20:01 UTC

Re: os-freebsd/488: Very slow response times . (fwd)

The following reply was made to PR os-freebsd/488; it has been noted by GNATS.

From: Marc Slemko <ma...@znep.com>
To: apbugs@apache.org
Subject: Re: os-freebsd/488: Very slow response times . (fwd)
Date: Sun, 27 Apr 1997 13:17:46 -0600 (MDT)

 
 ---------- Forwarded message ----------
 Date: Sun, 27 Apr 1997 20:27:19 +0200
 From: Patrick Boden <bo...@icl.lu>
 To: Marc Slemko <ma...@znep.com>
 Subject: Re: os-freebsd/488: Very slow response times .
 
 The server has been fixed . We got a new cpu and added more memory . Can
 you tell me what sotware you were using to test things . Here is some new
 stuff from the machine : 
 
 
 [543]nero@virtual(/usr/home/nero)#limit
 cputime         unlimited
 filesize        unlimited
 datasize        65536 kbytes
 stacksize       8192 kbytes
 coredumpsize    unlimited
 memoryuse       30940 kbytes
 descriptors     1800 
 memorylocked    20630 kbytes
 maxproc         1800 
 
 
 MAXUSER is at 128 users.  
 So all probs should be solved.
 
 		Let me know things ..
 
 		Patrick 
 
 ----------
 > From: Marc Slemko <ma...@znep.com>
 > To: Patrick Boden <bo...@icl.lu>
 > Cc: apbugs@apache.org
 > Subject: Re: os-freebsd/488: Very slow response times .
 > Date: Sonntag, 27. April 1997 08:21
 > 
 > On Sat, 26 Apr 1997, Patrick Boden wrote:
 > 
 > > >Environment:
 > > FreeBSD 2.1.5-RELEASE #0
 > > gcc 2.6.3
 > > Server generates around 12.000 unique hits a day and has aroud 700 Megs
 of transfer a day 
 > > >Description:
 > > My error logs show : 
 > > [Sun Apr 27 01:08:12 1997] access to
 /usr/local/www/virtual/video/public_html/cgi-video/videocounter.cgi failed
 for 208.154.142.3, reason: couldn't spawn child process
 > 
 > Please see the documentation, specifically the page at:
 > 	
 > 	http://www.apache.org/docs/misc/perf-bsd44.html
 > 
 > You are probably either running into a file descriptor or process limit.
 > The CHILD_MAX and OPEN_MAX kernel config file options are the ones to
 look
 > at.