Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

I don't want to be forced into your damned warning policy 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Something like this: my %warnings; $SIG{WARN} = sub { print STDERR $_[0] if not $warnings{$_[0]}; $warnings{$_[0]} = 1}; Gabor
    --

    • Only works per-process.

      Most webservers are multiple processes with a limited lifetime (they often get killed after a fixed number of requests).

      Then there's the issue that most large sites have a server farm too...

      • Yes, it only works per-process and per-server, but in my experience (with 80+ servers running many mod_perl processes) it is a very simple and effective way to eliminating the kinds of web-service log-storms you described. It changes an unmanageable flood into a very manageable stream. Highly recommended.

        • Sorry, didn't mean to imply that it doesn't mitigate the problem, it does but it can only mitigate it.

          Whether that turns the situation into a manageable one or not would depend on circumstance. :)

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.