aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zane silver (JIRA)" <>
Subject [jira] [Commented] (AURORA-1572) SIGTERM is not sent to child processes
Date Wed, 06 Jan 2016 20:49:40 GMT


zane silver commented on AURORA-1572:

Basically, I have several bash commands being executed in a process, i.e.

cmd = " <cmd 0> && <cmd 1> && ... <cmd n>"

In the case above, only "cmd 0" seems to receive the sigterm.

There's many workarounds for this... 
One solution would be to simply designate a separate aurora process for each cmd. Yet, each
command is tightly coupled to each other and it would be nice to have then all run together
as a single aurora process. etc...

> SIGTERM is not sent to child processes
> --------------------------------------
>                 Key: AURORA-1572
>                 URL:
>             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 file.

This message was sent by Atlassian JIRA

View raw message