> My CPU-based limiter is working quite nicely. It lets oodles of
> static pages be served, but if someone starts doing CPU intensive
> stuff, they get booted for hogging my server machine. The nice thing
> is that I return a standard "503" error including a "retry-after", so
> if it is a legitimate mirroring program, it'll know how to deal with
> the error.
choice!
> Doug - one thing I noticed is that mod_cgi isn't charging the
> child-process time to the server anywhere between post-read-request
> and log phases. Does that mean there's no "wait" or "waitpid" until
> cleanup?
it should be, mod_cgi waits for the child, parsing it's header output,
etc.
> Also, Doug, can there be only one $r->cleanup_handler? I was getting
> intermittent results until I changed my ->cleanup_handler into a
> push'ed loghandler. I also use ->cleanup_handler in other modules, so
> I'm wondering if there's a conflict.
you should be able to use any number of cleanup_handlers. do you have a
small test case to reproduce the problem?
