Sorry, upon rereading I see I expressed myself poorly. I meant to say that I need to be able to kill one and only one lineage of processes. At any given time, I may be executing 20 different threaded tests within the main executable. Each test will create a child (the shell) and a grandchild (the badly-behaved executable). I was concerned that if I killed the process group (changing the main's pgid to avoid the axe), all currently running executables, not just the failing one, would be killed. Hence, killing the process group would mean one failing test may take 19 good ones out with it.

Please correct me if I am ill-informed.

In reply to Re^4: Handling badly behaved system calls in threads by kennethk
in thread Handling badly behaved system calls in threads by kennethk

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.