The reason IPC examples are complicated is because IPC is complicated! Think about all the ways that either the parent or the child can end, and how each is to be notified of the other's death.

That said, you might be able to get away with the following (mostly pseudo-) code:

my $pid = fork();
if ($pid) {
  # in the parent
  wait for a keypress via your favourite method here
  if an abort occurs..
    kill 15, $pid;   # sigspec to taste
    exit;  # parent is done

  # you'll probably want POSIX WNOHANG here, otherwise waitpid will bl
+ock
  waitpid, $pid  # child exited normally  


} elsif (defined $pid) {
  # in the child
  system("run_groovy_command");
  exit; # tell daddy i'm done

} else {
  die "Cannot fork: try spoon\n";

}

[download]

In reply to Re: How to kill forked process by moot
in thread How to kill forked process by redss

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.