Hi, Excuse me for posting to this old threat, but I run in a similar situation where IPC::Run and Log::Log4perl were combined. I must remark that the title is actually misleading because no one has mentioned log4perl in his/her solution. Thus I will:
use IPC::Run qw(run new_chunker); # snip-snap-snip # ... my @cmd = qw(find /usr/bin -type f); run(\@cmd, "1>", new_chunker, \&logSdtout, "2>", new_chunker, \&logSdt +err); sub logSdtout { $logger->info(@_); } sub logSdterr { $logger->error(@_); }
edit: you need to pass the filter "new_chunker" to IPC::Run to break the output from your external program into newlines. Otherwise you will run into strange exceptions (undefined values) causing IPC::Run to fail. Cheers, Daniel

In reply to Re^5: Best practice ipc and Log::Log4perl by jointwork
in thread Best practice ipc and Log::Log4perl by codeacrobat

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.