RE: [Persistentperl-users] Logging with perperl

[Garth B. <gbe...@bl...>]

I am porting over piece by piece, so we have both mod_perl and
mod_persistentperl

Our httpd.conf:
...
ErrorLog /home/blueserver/logs/error_log
LogLevel warn
...
<Files *.pl>
    SetHandler perl-script
    PerlHandler Apache::Registry
    PerlLogHandler Apache::SizeLimit
    Options ExecCGI
</Files>

LoadModule persistentperl_module
/home/blueserver/bin/mod_persistentperl.so
<Files *.perpl>
    SetHandler persistentperl-script
    Options ExecCGI
</Files>
...

I copied the .pl files and to .perpl, and changed '!/usr/bin/perl' to
'#!/usr/bin/perperl -- -r4 -t10 -g' in those files.

In the mod_perl world, all warns and stuff would go to the apache
ErrorLog.  This would be the best solution with perperl, but I can live
with all the output going to a single file.  Where is the output of
warns, run through apache, suppose to go?  My guess is that the backend
pipes stderr to some unknown place....??

When using mod_persistentperl, what is the recommended setup for Carp,
or logging in general?

Sorry for not including the setup in the original message.

By the way, I have tried twice to set myself up on the mailing list by
entering my info here:
http://lists.sourceforge.net/lists/listinfo/persistentperl-users.  I
never received a confirmation email.  Any reason you know of why I
couldn't?

-----Original Message-----
From: Sam Horrocks [mailto:sa...@da...]=20
Sent: Tuesday, May 13, 2003 5:03 PM
To: Garth Benedict
Cc: per...@li...
Subject: Re: [Persistentperl-users] Logging with perperl=20


What do you mean by "normally".  Where do you expect to see the error
output? On the screen?  In the apache error log?

Are you using mod_persistentperl or the perperl binary?

 > I am trying to move out mod_perl infrastructure to Persistent perl.
I  > am having a horrible time tracking down errors.  warn statements do
not  > appear anywhere.  >  > I have tested 'use Carp', 'use CGI::Carp'
(with and without carpout),  > 'Apache::warn', and plain 'warn'.  I
cannot track down any of the  > output.  Is there a directive for
perperl to make it log "normally".  >  > Thanks for any help.  >  > ~~
> Garth Benedict  > Bluesocket, Inc  > (781) 328-0888x214