From: Vasily Kulikov <segoon@openwall.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-man <linux-man@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: For review: pid_namespaces(7) man page
Date: Thu, 28 Feb 2013 18:24:40 +0400 [thread overview]
Message-ID: <20130228142440.GA6328@cachalot> (raw)
In-Reply-To: <CAKgNAki=mUYuu_Ewhe7sjCmo+Dq2Vr+FZCixqNRaadcvAxtpFw@mail.gmail.com>
Hi Michael,
On Thu, Feb 28, 2013 at 12:24 +0100, Michael Kerrisk (man-pages) wrote:
> The namespace init process
> The first process created in a new namespace (i.e., the process
> created using clone(2) with the CLONE_NEWPID flag, or the first
> child created by a process after a call to unshare(2) using the
> CLONE_NEWPID flag) has the PID 1, and is the "init" process for
> the namespace (see init(1)). Children that are orphaned within
> the namespace will be reparented to this process rather than
> init(1).
Probably it worth noting here that this is true unless
prctl() with PR_SET_CHILD_SUBREAPER option is called.
Thanks,
--
Vasily Kulikov
http://www.openwall.com - bringing security into open computing environments
next prev parent reply other threads:[~2013-02-28 14:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 11:24 For review: pid_namespaces(7) man page Michael Kerrisk (man-pages)
2013-02-28 14:24 ` Vasily Kulikov [this message]
2013-03-01 8:03 ` Michael Kerrisk (man-pages)
2013-03-01 8:36 ` Eric W. Biederman
2013-03-01 8:53 ` Michael Kerrisk (man-pages)
2013-02-28 15:24 ` Eric W. Biederman
2013-03-01 8:50 ` Michael Kerrisk (man-pages)
2013-03-01 9:10 ` Eric W. Biederman
2013-03-01 10:20 ` Michael Kerrisk (man-pages)
2013-03-01 4:01 ` Rob Landley
2013-03-01 6:58 ` Eric W. Biederman
2013-03-01 9:57 ` Michael Kerrisk (man-pages)
2013-03-01 15:35 ` Eric W. Biederman
2013-03-04 12:46 ` Michael Kerrisk (man-pages)
2013-03-04 17:52 ` Eric W. Biederman
[not found] ` <CAKgNAkjYmvjMzC+nYqsjHf4bQn2ZwdE5wawoP2p32ZSo+0dfcQ@mail.gmail.com>
2013-03-05 6:23 ` Michael Kerrisk (man-pages)
2013-03-05 6:41 ` Eric W. Biederman
2013-03-05 8:37 ` Michael Kerrisk (man-pages)
2013-03-06 0:40 ` Eric W. Biederman
2013-03-07 8:20 ` Michael Kerrisk (man-pages)
2013-03-07 8:31 ` Eric W. Biederman
2013-03-06 1:58 ` Rob Landley
2013-03-06 2:23 ` Eric W. Biederman
2013-03-04 3:50 ` Rob Landley
2013-03-04 4:03 ` Eric W. Biederman
2013-03-04 12:48 ` Michael Kerrisk (man-pages)
2013-03-04 19:27 ` Rob Landley
2013-03-05 7:01 ` Michael Kerrisk (man-pages)
2013-03-04 12:50 ` Michael Kerrisk (man-pages)
-- strict thread matches above, loose matches on Subject: below --
2014-08-20 23:38 Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130228142440.GA6328@cachalot \
--to=segoon@openwall.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox