Beau E. Cox wrote:
Well Stas, you asked for it... :)
[...]
As you have figured out by trial and error, if you wanted the logger to work for everything you just needed to add:#-------------------mod_perl 2.0 rocks test--------------------------------- Alias /perl/ /srv/www/conf/perl/ <Location /perl/> SetHandler perl-script PerlResponseHandler ModPerl::Registry PerlOptions +ParseHeaders Options +ExecCGI </Location>#-------------------MyApache-FileLogger------------------------------------- <Location /> SetHandler perl-script PerlResponseHandler ModPerl::Registry PerlLogHandler MyApache::FileLogger Options +ExecCGI </Location>
> <Location />
> PerlLogHandler MyApache::FileLogger
> </Location>
what you originally did, is assigned ModPerl::Registry to serve everything on the server, but fed it with html and images, forgetting that it requires a Perl diet. Since you've repeated many times that you are a newbie, I'll forgive you ;) But if you weren't a newbie and you didn't remember to check the error_log file, I'd say: "shame on you" :) As the latter would have revealed the problem right away, from the first test.
Notice that my example configuration is correct since it demonstrates the use of a logger for a particular sub-section of the site that *happens* to be served by the ModPerl::Registry handler. Perhaps that example needs some extra notes to avoid this kind of confusion in the future. I'll add a note.
__________________________________________________________________
Stas Bekman JAm_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
