Re: Apache::PerlRun flooding error log

[prev] [thread] [next] [Date index for 2005/04/06]

Sounds great - yet obvious. I would have to do about 2 years worth of
work to fix all of the bugs. I didn't create them either, I fix them in
my own code - but we have so much code base. I wanted a mod_perl
solution to overcome this issue by filtering the error.

DJ

On Tue, 2005-04-05 at 22:06 -0400, Stas Bekman wrote:
> David J Radunz wrote:
> > Heya All,
> >=20
> >   I have an issue at the moment where if there is an error/warning =
in my
> > PerlRun script/module then the error/warning is printed as well as =
the
> > entire contents of the script being eval'ed. This only occurs when a
> > string is evaled and Carp stack trace is on.=20
>=20
> David, why not fix errors and warnings and have nothing logged at all?
>=20
> Why do you set:
>=20
> $SIG{__DIE__} =3D \&Carp::confess;
> $SIG{__WARN__} =3D \&Carp::cluck;
>=20
> Those are used for development, not production env.
>=20
> As you've figured it's how perl works, mod_perl doesn't do anything=20
> special about it.
>=20

This email and any files transmitted with it are confidential and =
intended solely for the=20
use of the individual or entity to whom they are addressed. Please =
notify the sender=20
immediately by email if you have received this email by mistake and =
delete this email=20
from your system. Please note that any views or opinions presented in =
this email are solely
 those of the author and do not necessarily represent those of the =
organisation.=20
Finally, the recipient should check this email and any attachments for =
the presence of=20
viruses. The organisation accepts no liability for any damage caused by =
any virus=20
transmitted by this email.=20