[
https://issues.apache.org/jira/browse/AURORA-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086289#comment-15086289
]
Stephan Erb commented on AURORA-1572:
-------------------------------------
If you are linking your commands using {{&&}} only one will be running at any
given time. When {{<cmd n>}} returns with return code 0, {{<cmd n+1>}} will be
executed. Sending a SIGTERM to a process tends to result in a return code !=
0, so I don't really see the problem you are describing.
Do you have a minimal reproducing example (either in Aurora or using {{bash -c
"..."}} directly)?
> 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)
