You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2017/09/28 18:49:01 UTC

[jira] [Commented] (MESOS-8037) ns::clone should spawn process, which is a direct child

    [ https://issues.apache.org/jira/browse/MESOS-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184641#comment-16184641 ] 

Vinod Kone commented on MESOS-8037:
-----------------------------------

[~jieyu] What's your opinion on this?

> ns::clone should spawn process, which is a direct child
> -------------------------------------------------------
>
>                 Key: MESOS-8037
>                 URL: https://issues.apache.org/jira/browse/MESOS-8037
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Andrei Budnik
>
> `ns::clone` does double-fork in order to be able to enter given PID namespace and returns grandchild's pid, which is not a direct child of a parent process, hence parent process can not retrieve status of an exited grandchild process.
> As second fork is implemented via `os::clone`, we can pass `CLONE_PARENT` flag. Also, we have to handle both intermediate child process and grandchild process to avoid zombies.
> Motivation behind this improvement is that both `docker exec` and `LXC attach` can enter process' PID namespace, while still controlling child's status code.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)