You may want to consider using on of the logging frameworks, available on CPAN, as opposed to a print based approach
Log::Log4perl, Log::Any, Log::ger are examples that support directing output of the log statements to different locations based upon a category. A category is generally a package but can be explicitly set as desired.
Here an example from the Log::ger::Manual::Tutorial::05_Category tutorial
use Log::ger::Output Composite => (
outputs => {
File => [
{
conf => {path=>'/path/app.log'},
category_level => { Foo => 'off' },
},
{
conf => {path=>'/path/foo.log'},
level => 'off',
category_level => { Foo => 'trace' },
},
],
},
);
lbe
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.