Normally, unless the child processes detach from the parent's process group, signals will propagate to the children, so when you kill the parent, the children should go down as well. However, if you want to do this explicitely, you can use Proc::ProcessTable. Something like this (untested):
use strict; use warnings; use Proc::ProcessTable; my $signal=15; my $parent=shift; # Parent PID from args my $proc_table=Proc::ProcessTable->new(); foreach my $proc (@{$proc_table->table()}) { kill($signal, $proc->pid) if ($proc->ppid == $parent); }
Making this code recursive to kill the children's children is left as an exercise for the reader :) (read: it's Sunday morning and I can't be bothered to do so myself ;) ).

CU
Robartes-


In reply to Re: Killing child process by robartes
in thread Killing child process by hotshot

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.