Jim,
Thanks for your reply. Yes,
that was my post to perlmonks. set_progname() is a function in the Carp module
that lets you set/reset the name of the Carping script; that way you know which
script generated the logged event. Another way is to pass
"name=scriptX" to
o. Give it a try, and
please let me know whether this solution gives you any traction.
Cheers!
-Jim
On Fri, 27 Jan 2012, Brett Lee wrote:
Hi Folks,
Running several scripts under ModPerl::Registry that use CGI::Carp. Am
seeing problems with the logging. The message that is logged is co
Hi Folks,
Running several scripts under ModPerl::Registry that use CGI::Carp. Am seeing
problems with the logging. The message that is logged is correct, however the
name of the script that generated the event is not.
Each script contains a line similar to:
use CGI::Carp qw(name=my_script_X
Arshavir Grigorian wrote:
Hello list,
Not sure when this started happening, but at some point calling
CGI::Carp::carp() started resulting in deep recursion within
CGI::Carp::warn() eventually killing the process. I think the recursion
is caused by the following:
$main::SIG{__WARN__}=\&
Hello list,
Not sure when this started happening, but at some point calling
CGI::Carp::carp() started resulting in deep recursion within
CGI::Carp::warn() eventually killing the process. I think the recursion
is caused by the following:
$main::SIG{__WARN__}=\&CGI::Carp::warn;
sub real
e under mod_cgi. CGI::Carp's
documentation claims to have long ago been patched to work with
mod_perl,
I suppose it assumed mod_perl handlers, but may be not PerlRun.
but for some reason this isn't working for me. Even a very
simple example:
#!/usr/bin/perl -w
use CGI::Carp 'fa
mod_cgi. CGI::Carp's
documentation claims to have long ago been patched to work with
mod_perl, but for some reason this isn't working for me. Even a very
simple example:
#!/usr/bin/perl -w
use CGI::Carp 'fatalsToBrowser';
die 'CGI::Carp test';
will log this in error_log:
[Thu
