httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <>
Subject Re: cvs commit: apache-1.3/src/main http_main.c
Date Sun, 03 Jan 1999 22:28:25 GMT
Yea, I don't know that this is a good thing to do by default either.
However, I keep running into situation after situation where something
screws this up.  Perhaps the code I'm dealing with is too horrible, but
I really don't think that is the case.

I would go for a compile time (yuck yuck, compiletime bad) or runtime
config option to enable a "reset alarm and handler" call at the end of
each response, but default to off.

On Sun, 3 Jan 1999, Roy T. Fielding wrote:

> >-1.  I'm backing this out.  Any such problems are problems with 3rd party
> >modules and libraries, and it is the module implementor's job to fix them. 
> >Furthermore, this doesn't cover all the crap a library/module could fuck
> >up, like setrlimit().  Surely you're not going to cover a libraries butt
> >in that area... just like we don't do anything to close all the
> >descriptors not listed in a pool.  If a library/module NEEDS this cleanup
> >then they can damn well register a cleanup.
> Okay by me -- I was just trying to fix the problem that Marc mentioned
> a while back.  It is more likely to occur with database libraries than
> anything else, so I suppose a database interface module like mod_php
> could handle it on their own.  This is one hell of a hard thing to debug
> though.
> ....Roy

View raw message