G'day Monks,
I have a question is it possible to pass all STDERR into a logger function? I want to log any errors from supporting modules into my application log to be able to correlate what the application was doing when the error occurred.
Any suggestions would be greatly appreciated and thanks in advance.
Danny

Here is my logger function, the Date() function provides the timestamps for log file name and log entry. What I was hoping to do is something like this Logger(STDERR) 

sub Logger()
{
        my $message = $_[0];
        if ( $message eq "" )
        {
            return;
        }
        &Date();
        $pdmgrdFile = "pdmgrd\.$LOG_NAME";
        $pdmgrdLogPath = "$log$pdmgrdFile";
        open(PDMGRD, ">>$pdmgrdLogPath") || die "Can't open logfile: $
+pdmgrdLogPath - $!\n";
        print PDMGRD "$LOG_STAMP $message\n";
        close(PDMGRD);
}

[download]

In reply to Log STDERR by onegative

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.