I have a multi threaded Perl script (master-workers architecture) in which the workers call an external application and need to process the standard output and standard error. I tried Capture::Tiny but that crashed the worker threads if a lot of workers were busy processing. Now, I use IPC::Run3 but this also fails, although less often as Capture::Tiny. Is there a safe way to call external applications from parallel running worker threads and being able to process the standard output and standard error? The idea is that the external calls can run in parallel so semaphore locking seems not the way to go to me. My current run3 call
my @spaziooptions = ($spaziocmd, "-m" , $transref->{'QMANAGER'} ,"-q"
+, $destination_queue, "-i" , $transref->{'POLLERFILE'} ,"-d" , $desti
+nation_filename , "-k" , $transref->{'DATATYPE'}, "-s", $global_hostn
+ame, "-c", $cor_id);
my $cmdout;
my $cmderr;
run3 \@spaziooptions, \undef, \$cmdout, \$cmderr;
my $cmdexit = $?;
-
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.