Beau E. Cox wrote:
Hi -
In: http://perl.apache.org/docs/2.0/user/handlers/http.html#PerlLogHandler,
the PerlLogHandler documentation, the configuration file sample setup is
given as:
SetHandler perl-script
PerlResponseHandler ModPerl::Registry
PerlLogHandler MyApache::LogPerUser
Options +ExecCGI
Now I wrote a simple log handler and had no end of problems (will detail
upon request) with this configuration.
Please do so.
Since I want to intercept
_every_ access to my server, I ended up with:
PerlLogHandler MyApache::Logger
and then shortened it to:
PerlLogHandler MyApache::Logger
where MyApache::Logger is the name of my logging perl script. I works
perfectly.
Do you really need all the other 'stuff'? Since this is a log handler
why would you need the ResponseHandler, etc.?
Of course you don't need it. I've added it so the example will be
complete (i.e. you need some kind of response handler, or I guess you
could rely on the default handler)
As you have gathered, this is my very first mod_perl handler :)
You probably want to get hold of the eagle and the R&W mod_perl books.
Though covering mod_perl 1.0, most of the information you learn applies
to 2.0 as well. Think of 2.0 as 1.0 on mushrooms. For the books info
see: http://perl.apache.org/docs/offsite/books.html#Learn_mod_perl
PS: Hey Mr. 100%, mod_perl 2.0 rocks!
;)
p.s. Geoff, we need a short acronym for your book so it's easy to refer
to it, (a new eagle), I've called it R&W (Red&White), if you have a
better idea, please suggest.
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com