www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guy St-Amant <gstam...@flaphil.com>
Subject Re: general/5001: Large number of site overflows frontpage extensions in Apache 1.3.3
Date Mon, 13 Sep 1999 02:10:00 GMT
The following reply was made to PR general/5001; it has been noted by GNATS.

From: Guy St-Amant <gstamant@flaphil.com>
To: marc@apache.org
Cc: apbugs@apache.org
Subject: Re: general/5001: Large number of site overflows frontpage
  extensions in Apache 1.3.3
Date: Sun, 12 Sep 1999 21:59:25 -0400 (EDT)

 THank's for the help.  I actually found out what the problem was.  It has
 nothing to
 do with the frontpage.  It just happened to seem to come from Fronpage.
 
 My problem was that the Apache engine is a single process that spawns child
 processes.  My SCO box was set to 110 files/per process.  Since I was
 opening two
 files per virtual website (error_log,access_log).  I quickly ran out of
 available
 files for the Apache process.  So I temporarely deleted the error_log files from
 the conf.httpd config.  And I will increase the limit of open files per
 process in
 the Kernel.
 
 Thank's for all your help.  Please continue doing all this great work on the
 Apache project.
 
 
 Guy St-Amant
 GSTA Internet.
 
 
 At 15:54 09/12/99 -0000, you wrote:
 >[In order for any reply to be added to the PR database, ]
 >[you need to include <apbugs@Apache.Org> in the Cc line ]
 >[and leave the subject line UNCHANGED.  This is not done]
 >[automatically because of the potential for mail loops. ]
 >[If you do not include this Cc, your reply may be ig-   ]
 >[nored unless you are responding to an explicit request ]
 >[from a developer.                                      ]
 >[Reply only with text; DO NOT SEND ATTACHMENTS!         ]
 >
 >
 >Synopsis: Large number of site overflows frontpage extensions in Apache 1.3.3
 >
 >State-Changed-From-To: open-closed
 >State-Changed-By: marc
 >State-Changed-When: Sun Sep 12 08:54:27 PDT 1999
 >State-Changed-Why:
 >Erm... we have nothing to do with the frontpage extensions
 >and can do nothing to fix their broken nature.
 >
 >What most sites using a larger number of virtual hosts do
 >is generate a fake config file for each vhost and point
 >the fp extensions for a particular site to that specific
 >config file.  That is MS's problem.
 >
 >
 

Mime
View raw message