[snip]
> >
> > Another question, do you (or anyone else for that matter) know how the
> > accesslog works? (and also why it does work like it does) It seems it
> > prints after the request is done, otherwise could that easily be used
> > for checking the parameters, and not only loging.
>
> You
Jon Molin wrote:
> Stas Bekman wrote:
>
>>It's actually easy, take a look at the Apache::SizeLimit or
>>Apache::GTopLimit, look at the cleanup handler that they register. Now
>>take this handler and dump whatever you need to the file or error_log
>>when you find that the process was taking too m
Stas Bekman wrote:
>
> It's actually easy, take a look at the Apache::SizeLimit or
> Apache::GTopLimit, look at the cleanup handler that they register. Now
> take this handler and dump whatever you need to the file or error_log
> when you find that the process was taking too much memory.
>
> Tak
Jon Molin wrote:
> Hi list,
>
> I had problems with a script that went nuts and took 65MB memory and
> alot of cpu. To track this script down I thought Apache:VMonitor would
> be perfect, unfortenately I ran into some weird promlems (it said there
> was an error in mod_perl.h) and i know gcc mig
