For the most part I agree with {NULE}. I generally do something similar, but like podmaster I generally put in levels so log 3, $message only prints if the log level is 3 or greater. I have also created systems where I send the data to syslog (both on *nix and win32) at facility LOG_LOCAL0. This allows configuring the log behavior without editing the perl script. This is important for programs that run continuously. I even sometimes have the program respond to signals or other user input to chnage the log level at run time. There are multiple syslog modules on cpan, and activestate ships with syslog.pl (which requires a syslog.ph unless you hack it) for Windows.

HTH, --traveler

In reply to Re: naming conventions for logs by traveler
in thread naming conventions for logs by aufrank

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.