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 much memory. >> >>Take a look at this code and you will see that it's very simple. >> >> > > Thanks a bunch, I'll look into that. > > 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 probably need to read some docs, which explain how can specify your own access log format or supply your own log handler. For using the standard Apache formats see the docs at apache.org (you also have them installed together with Apache under 'manual' dir on your machine. For mod_perl examples you should probably see the eagle book, check www.modperl.com (which seems to be offline now) if it has the relevant chapters online, I think it's chapters 7 and 9 that you want. The guide has some info here: http://thingy.kcilink.com/cgi-bin/modperlguide.cgi?q=PerlLogHandler _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
