On Tue 01 Sep 2009, Sebastiaan Hoogeveen wrote:
> Not sure if this would fix your problem, but you can just set $0 from
> within the mod_perl module to whatever you'd like to show up in the
> process list, just as with a regular perl script. It probably depends
> on the OS you're running whether
Hi Fred,
Decided to look at the source found by your 'ack'.
It turns out that, in file pad.c, someone in the perl 5.10.0 or 5.10.1
project decided that the Perl_pad_sv routine was only needed if
-DDEBUGGING was specified for the Perl build.
Fixed this by commenting out the #ifdef DEBUGGING at l
cr...@animalhead.com wrote:
I have always included previous perl libraries in the @INC of
new builds. And it has always worked, with the single
exception of building mod_perl2 this time. All of the perl
scripts and modules on my site work well under the new 5.10.1.
Pure Perl modules should w
On Sep 2, 2009, at 6:21 AM, Michael Peters wrote:
cr...@animalhead.com wrote:
I have always included previous perl libraries in the @INC of
new builds. And it has always worked, with the single
exception of building mod_perl2 this time. All of the perl
scripts and modules on my site work we
Hi
We recently started seeing this appearing in our logs as well, and I'm not
sure what's causing it. We didn't change our software in any way that I can
see would have caused this to start happening, so it's quite odd.
Did you work out what was causing it?
Rob
- Original Message -
