fast:

If you use fork (on an operating system that supports it well), you can set up the I/O streams and fork off the task. Then you'll have the PID (process identifier) for the forked job, and you can kill it when you decide to. Something like:

my $child_PID = fork;
if ($child_PID == 0) {
   # We're in the child process, so redirect I/O handles and run progr
+am...
   close STDOUT;
   open STDOUT, '>', 'foobar.log' or die $!;
   exec 'foobar.exe', 'argument_1', 'second argument', 'etc...';

   die "Couldn't find foobar.exe!";    # should never get here...
}
else {
   # We're in the parent, so wait a few seconds, and kill the child.
   sleep 10;
   kill 9, $child_PID;
}

[download]

Untested code. Testing (and any repairs required) left as an exercise for the reader...

...roboticus

In reply to Re: Run and Stop another program in perl by roboticus
in thread Run and Stop another program in perl by fast

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.