mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Pavel Emelyanov" <xemul@openvz.org>
Cc: "Kir Kolyshkin" <kir@openvz.org>,
	linux-man@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Documentation for CLONE_NEWPID
Date: Tue, 25 Nov 2008 11:27:33 -0500	[thread overview]
Message-ID: <cfd18e0f0811250827q71b4f07l33821d004f27adf3@mail.gmail.com> (raw)
In-Reply-To: <492C1FCB.1080405@openvz.org>

Hi Pavel,

[...]

>> *** Here's where I make the point about each process having multiple PIDs"
>>
>>>> +The existence of a namespace hierarchy means that each process
>>>> +may now have multiple PIDs:
>>>> +one for each namespace in which it is visible.
>>
>> I added some words here:
>>
>> "each of these PIDs is unique within the corresponding namespace".
>
> Correct.

Thanks for the ACK.

>>>> +(A call to
>>>> +.BR getpid (2)
>>>> +always returns the PID associated with the namespace in which
>>>> +the process was created.)
>>> I don't thinks it's a good example - the getpid cannot be called
>>> for other process other than current :)
>>
>> It wasn't meant as an example.  The point was, with a process
>> potentially being a member of multiple namespaces, the reader might
>> wonder: what does getpid(2) return?  This sentence was intended to
>> clarify that.  With that explanation, does this sentence now seem
>> okay?
>
> Yes, but I'd change "was created" into "lives in". From my POV this
> sounds more clear. I do not insist however :)

Done.

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html

      reply	other threads:[~2008-11-25 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19  2:59 Michael Kerrisk
2008-11-23 22:20 ` Serge E. Hallyn
2008-11-25 15:09   ` Michael Kerrisk
2008-11-26 17:08     ` Serge E. Hallyn
2008-11-24 12:46 ` Pavel Emelyanov
2008-11-25 15:46   ` Michael Kerrisk
2008-11-25 15:54     ` Pavel Emelyanov
2008-11-25 16:27       ` Michael Kerrisk [this message]

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=cfd18e0f0811250827q71b4f07l33821d004f27adf3@mail.gmail.com \
    --to=mtk.manpages@googlemail.com \
    --cc=kir@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=xemul@openvz.org \
    /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

all inboxes | Powered by JetHome®