[
https://issues.apache.org/jira/browse/AURORA-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086275#comment-15086275
]
John Sirois edited comment on AURORA-1572 at 1/6/16 9:05 PM:
-------------------------------------------------------------
The example you give does not seem to match the description well. In your
example only {{cmd0}} is an active process when the signal is received ({{&&}}
chain, not a pipeline, etc). As such - even if SIGTERM were sent to the full
process tree - that's still just {{cmd0}} here and if it handles the signal by
exiting 0, the {{&&}} chain will continue on to {{cmd1}}, etc.
was (Author: jsirois):
The example you give does not seem to match the description well. In your
example only {{cmd0}} is an active process when the signal is received ({{&&}}
chain, not a pipeline, etc). As such - even if SIGTERM were sent to the full
process tree - that's still just {{cmd0}} here and if it handles the signal by
not exiting 0, the {{&&}} chain will continue on to {{cmd1}}, etc.
> SIGTERM is not sent to child processes
> --------------------------------------
>
> Key: AURORA-1572
> URL: https://issues.apache.org/jira/browse/AURORA-1572
> Project: Aurora
> Issue Type: Story
> Components: Executor
> Reporter: zane silver
> Assignee: Bill Farner
> Priority: Trivial
>
> In terminate_process, SIGTERM is sent to the parent process only. This seems
> like a deliberate design choice given that the kill_process does send a
> SIGKILL to each child process. Is there a reason why SIGTERM is not also sent
> the to child processes?
> For reference, I'm referring to the functions defined in the thermos
> helper.py file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
