On Mon, 2009-03-02 at 10:20 -0500, Perrin Harkins wrote:
> On Mon, Mar 2, 2009 at 9:54 AM, Matthew Lenz wrote:
> > According to the docs CGI::Carp doesn't function properly with
> > fatalToBrowser under mod_perl 2.
>
> I'm not sure if that's accurate or not, b
As I've mentioned in previous posts, I'm migrating from an older
environment to a new environment with mod_perl 2.
With mod_perl 1.x we had VERY OLD customised version of CGI::Carp (with
fatalsToBrowser) printing an error to the browser AND sending an email
with backtrace and environment informati
On Fri, 2009-02-27 at 11:29 -0500, Perrin Harkins wrote:
> On Fri, Feb 27, 2009 at 7:58 AM, Matthew Lenz wrote:
> > I looked through the packge diff:
> >
> > http://ftp.de.debian.org/debian/pool/main/liba/libapache2-mod-perl2/libapache2-mod-perl2_2.0.4-5.diff.gz
> &
On Thu, 2009-02-26 at 17:17 -0500, Perrin Harkins wrote:
> On Thu, Feb 26, 2009 at 4:01 PM, Matthew Lenz wrote:
> > Maybe the debian guys did something goofy with the modules. It wouldn't
> > be the first time. That or maybe its just a bug in ModPerl. Even if
> > some
On Thu, 2009-02-26 at 15:49 -0500, Adam Prime wrote:
> André Warnier wrote:
> > Matthew Lenz wrote:
> >> I can't seem to disable warnings on our production environment. 'use
> >> warnings' is not included in any of the config/startup/scripts or custom
&g
I can't seem to disable warnings on our production environment. 'use
warnings' is not included in any of the config/startup/scripts or custom
modules. Its possible I guess that its being used by a CPAN module.
We had a system on Debian 3.1 (apache/mod_perl 1.x)and I have been doing
work to migra
