Received: (from majordom@localhost) by hyperreal.com (8.8.5/8.8.5) id NAA25435; Sat, 28 Jun 1997 13:17:23 -0700 (PDT) Received: from twinlark.arctic.org (twinlark.arctic.org [204.62.130.91]) by hyperreal.com (8.8.5/8.8.5) with SMTP id NAA25428 for ; Sat, 28 Jun 1997 13:17:19 -0700 (PDT) Received: (qmail 1528 invoked from network); 28 Jun 1997 20:16:05 -0000 Received: from benchlark.arctic.org (206.221.201.235) by twinlark.arctic.org with SMTP; 28 Jun 1997 20:16:05 -0000 Date: Sat, 28 Jun 1997 13:17:29 -0700 (PDT) From: Dean Gaudet To: new-httpd@apache.org Subject: Re: Making RLimitMEM and RLimitCPU work for httpd children In-Reply-To: <9706261628.AA5317@circus.med.iacnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org I took a look at this George, your example makes it seem like the Rlimit applies only to things in /cgi-bin. But I'm guessing the code imposes these limits process wide all the time, so it's slightly misleading. In order to integrate something like this into the server as a feature we'd need a directive that says "apply resource limits to httpd child in addition to cgis". And it'd be nice if it could use getrusage() to setrlimit() appropriate soft values on a per-request basis (and then remove the limits at the end of the request). That would be a cool feature to have. Dean P.S. We need context diffs (diff -c3) to apply things against HEAD. On Thu, 26 Jun 1997, George Carrette wrote: > Because application developers here are making heavy use of the Perl Module > I found it *prudent* to modify the apache 1.2.0 so that RLimitMEM and RLimitCPU > because it is fairly easy to get into infinite loops in perl programs, > especialling when using CGI.pm, evidently. > > The changes are described here: http://cpartner.iacnet.com/apache/ > along with changed files and differences between these files > and the original 1.2.0 sources. > > Pretty limited changes actually. >