Re: Apache::PerlRun flooding error log

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

Well, all of these scripts run under PerlRun - so I either have to make
that change in every one of them, and every module they load. Like, if I
set the SIG{__WARN__} at the top of a script and a module set it,
wouldn't it then be 'reset' ?

David

On Wed, 2005-04-06 at 01:00 -0400, Stas Bekman wrote:
> Stas Bekman wrote:
> > David J Radunz wrote:
> >=20
> >> 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.
> >=20
> >=20
> > If that's the case, why don't you adjust your %SIG wrappers to =
truncate=20
> > the error length? It's relatively easy:
> >=20
> > use Carp qw(confess cluck);
> > $SIG{__DIE__}  =3D sub { die  substr Carp::longmess(@_), 0, TRUNCATE =
};
> > $SIG{__WARN__} =3D sub { warn substr Carp::longmess(@_), 0, TRUNCATE =
};
>=20
> Sorry, it should have been:
>=20
> use constant TRUNCATE =3D> 40;
> use Carp ();
> $SIG{__DIE__}  =3D sub { die  substr Carp::longmess(@_), 0, TRUNCATE =
};
> $SIG{__WARN__} =3D sub { warn substr Carp::longmess(@_), 0, TRUNCATE =
};
>=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