What do you have against putting perl code in your config?

You know that you can keep your config in a string, modify it in the usual way, and then pass that string into Log::Log4perl::init. Something like this (from one of my scripts)

my $log4perlConf = q( log4perl.appender.scriptName.filename=__PLACEHOLDER__ log4perl.appender.scriptName.layout=Log::Log4perl::Layout::Pattern +Layout log4perl.logger = INFO, scriptName ); $log4perlConf =~ s/__PLACEHOLDER__/$logFileName/; Log::Log4perl::init(\$log4perlConf);

I don't think this approach will let you change the output file on the fly, though depending on what you are trying to do, you could also look into: Log::Dispatch::FileRotate which rotates the log file daily, weekly or whatever you like.


In reply to Re: Log4perl modifying filename by chrestomanci
in thread Log4perl modifying filename by rootcho

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.