<div dir="ltr">On Wed, Jan 11, 2012 at 16:26, André Scholz <span dir="ltr"><<a href="mailto:andre.scholz@uni-bremen.de">andre.scholz@uni-bremen.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(on unix) creating a process A which spawns itself a subprocess B and<br>
terminating process A before it finishes leaves process B as a process on its<br>
own. This is because "terminateProcess" sends the sigterm signal to the<br>
process only and not to its process group.<br></blockquote><div><br></div><div>terminateProcess passes on the semantics of kill(2); on SVID-compliant (and I think POSIX.1-compliant) systems, the negative of the process group leader's process ID is used to signal the process group. Note that you may need to arrange for your initial child process to invoke setpgrp() to insure that the parent program is not part of the process group.</div>
<div><br></div><div>However I'm unclear as to the situation you are encountering, as your example does not appear to be spawning an intermediate process.</div><div><br></div></div>-- <br>brandon s allbery <a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a><br>
wandering unix systems administrator (available) (412) 475-9364 vm/sms<br><br>
</div>