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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|