[jira] [Resolved] (MESOS-199) Attempting to use killtree.sh after forked pid has died is fruitless.

["Vinod Kone (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone resolved MESOS-199.
------------------------------

    Resolution: Fixed

https://reviews.apache.org/r/5260/
                
> Attempting to use killtree.sh after forked pid has died is fruitless.
> ---------------------------------------------------------------------
>
>                 Key: MESOS-199
>                 URL: https://issues.apache.org/jira/browse/MESOS-199
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Benjamin Hindman
>            Assignee: Vinod Kone
>            Priority: Blocker
>
> If specified '-g' and '-x' the killtree.sh script attempts to look up the group ID and session ID of the pid that is passed as an argument and kill all processes in the group and session as well. However, if the pid is no longer valid, then the script will do nothing because it can't determine the group ID or session ID!
> The process isolation module should hold onto the group ID and the session ID, and we should create a new script called killsess.sh that kills all processes in a session as well as simply invoke kill passing '-n' where n is the group ID.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira