httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: memory allocations stuff (question)
Date Wed, 09 Jul 1997 17:15:31 GMT
This is what I was hoping for:

    for(;;) {
	begin new request (read_request_line)
	calculate usage + max_usage_per_request
	do the request

That really only applies to the CPU usage limit though.  A memory limit
doesn't need to be recalculated per request.

As for directive names... how about ServerRLimitXXX.

It's too bad that there's no way to catch a signal when the soft limits
are reached and respond with a 5XX error.


On Wed, 9 Jul 1997, George Carrette wrote:

> (Stanley Gambarin)  asks:
> >Second: would it be reasonable to provide a limit on the maximum amount 
> >of memory that the server may allocate (this may prevent infinite loops
> >taking down whole machine with them).  The server may just exit if the 
> >maximum amount of memory is reached (configurable at runtime) ?
> If you apply the patches at
> then the RLimitMEM configuration parameter used in the global
> context in httpd.conf will be in effect for all children of the initial httpd
> process.
> Currently the RLimitMEM parameter only applies to cgi scripts
> and server-side-include exec statements.
> When a process runs out of RLimitMEM the result is that malloc returns NULL.
> I've been asked to invent new config parameter names before these
> patches can be applied to the Apache sources, but I haven't been
> able to think up a good name, nobody has suggested one,
> and I have a preference myself to cleaning up the documentation
> so that it is more carefully worded and accurate.

View raw message