Figure out which processes active should kill

[sburnett]

bismark-active should only run for a certain amount of time (400 seconds by default) before we kill it to reclaim resources.

Occasionally, D-ITG occasionally sticks around for too long and refuses to die when we kill its parent process. We should figure out why this is and/or the proper way to kill it.

[ggmartins]

Sam,

looking at the ITGRecv code it seems that "int terminate(int sign)" is not
considering any other active thread running except from gui. Checking the
code the typeParser functions seems to fire a few threads. So the problem
may be in there. Makes sense?

int terminate(int sign)
..
<------><------>if (sign == SIGINT)

<------><------><------>printf("Finish with CTRL-C! \n");

<------><------>

<------><------>else if (sign == SIGTERM)

<------><------><------>printf("Finish requested caused by errors! \n");

<------>}

<------>if (gui) {

<------><------>PRINTD(1, "terminate: Terminating thread waitStopKey and
exiting\n");
<------><------>terminateThread(waitStopKeyTid);

<------>}

<------>exit(0);

}

On Mon, Sep 16, 2013 at 1:40 PM, Sam Burnett notifications@github.comwrote:

bismark-active should only run for a certain amount of time (400 seconds
by default) before we kill it to reclaim resources.

Occasionally, D-ITG occasionally sticks around for too long and refuses to
die when we kill its parent process. We should figure out why this is
and/or the proper way to kill it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4
.

[wdd]

Which D-ITG component sticks around? ITGSend or ITGRecv?