This may be a little overblown for what you need, but it will capture both the STDOUT and the STDERR to a log file, die if the program does not exist, and display the return code.
#!/usr/bin/perl
use strict;
use warnings;
use IPC::Run qw( start pump finish );
open(LOG, '>', 'log') or die "Unable to open log: $!";
my ($in, $out);
my $h = start([ 'run_tool', '-f', 'test.tcl' ], \$in, \$out, \$out);
while($h->pump) {
print LOG $out;
$out = '';
}
$h->finish;
close(LOG);
print "Exit code was: " . $h->result . "\n";
You'll probably want to take a closer look at the
IPC::Run docs for more details on what all it can do. It also offers fairly flexible control over interactive programs if you want to do that in the future. I tend to use it over
open or
system any time I need to start doing anything more than just run the program.
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.