Well, a UNIX logging server would probably be the best solution.

Next best: I'm sure one of the UberMonks will post some kind of cool Carp overloading scheme that forks off a process to do error logging and wait for an exclusive lock on the file, without holding up your script.

But then there's my little kludge: I just set up an "errors" directory in each of my script directories, owned by the webuser. 
# TOP OF SCRIPT
use File::Basename;
my ($bname, $bpath, $bsuffix) = fileparse($0,'.pl','.cgi');
my $LOGFILE = "errors/$bname.txt";
if (-s $LOGFILE > 10000) { unlink $LOGFILE; }
open (STDERR, ">>$LOGFILE") or die "Couldn't open script log: $!\n";

[download]
It's not perfect, and race conditions exist. But, it works well enough for my needs -- I'm mainly concerned with just redirecting the errors so I don't get the evil 500, not so much with keeping track of the errors.

So, it would be easy enough to toss these errors out to a web-accessible directory and accomplish what you want.

In reply to Re: Running with warnings on a remote server by joealba
in thread Running with warnings on a remote server by Elliott

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.