Yeah, CGI::Carp will do exactly what you want. I trap all system errors
(DBI, die, etc) using Carp and format the results into a nice webpage for
the user and further, I email myself the error along with the environment
variables in use at the time as well as a stack dump of where it occured.
This
Yes, should be the same code. You could, of course, do wierd things in your
perl code to pick up different libraries, but I can't imagine you would do
that purposefully.
dale
- Original Message -
From: "Marc M. Adkins" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, June 07,
Assuming your CGI scripts aren't doing strange things, liking hanging around
after the session has closed and doing clean-up work, you might check your
httpd.conf settings on the number of threads and requests per threads. Its
possible that your httpd threads are short-lived and restarting more of
This appears to be the classic "global variable/uninitialized variable"
issue with your script. Mod_perl will load that script once and never
reload it again unless you tell it too, even when different users access
that script. If you have written a CGI script that doesn't lead itself to a
ready
I've dealt with fairly large sets, but not as static as yours. If your only
keys for searching are planet and date, then a perl lookup with a hash will
be faster overall since a DB lookup involves connecting to the database,
doing the standard prepare/execute/fetch which could be as costly (for a
Hey,
I have combed the various docs and haven't yet
found the silver bullet to turn off all the warnings I am getting from mod_perl
in my error_log that look something like this:
Constant subroutine
Apache::ROOTusa_2eusahire_2ecom::cgi_2dbin::portal::gojobs::gojobs_2ecgi::RC_CONTINUE
red
Trying to narrow down a problem I am having with mod_perl::PerlRun on a
stock RedHat 8.0 system, I have the following that simply doesn't work
reliably under Apache 2.0.40 and mod_perl-1.99_05-3. The script runs fine
for the first few refreshes and then I get the ominous error message:
Error mes
I want to raise my hand on this one too. I went and downloaded, compiled
and built and received the exact same problem on RedHat 8.0 with the same
versin of perl and mod_perl (no surprise). But I just don't have the time
or expertise to track down the exact reason by libapr.so isn't around or
bei
PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: RedHat 8.0 standard Apache2.0 and mod_perl 2.0::PerlRun
doesn't work?
Dale Lancaster wrote:
> I have searched the archives and various websites to find my problem and
> its associated resolution to no avail.
>
> I upgraded my working
I have
searched the archives and various websites to find my problem and its associated
resolution to no avail.
I
upgraded my working Apache 1.3 and mod_perl 1.x website using the PerlRun option
of modperl to the RedHat 8.0 standard release with Apache/mod_perl 2.0 combo --
bad move it ap
10 matches
Mail list logo
