[PATCH] docs: nsenter(1): fix further details in PID namespace section

[PATCH] docs: nsenter(1): fix further details in PID namespace section

[Stephen Kitt]

The "Further details" sentence in the PID namespace section got merged
with the surrounding text; this patch moves it to the end, to match
the other namespace sections, and adds the missing clone(2) reference.

Fixes: 894efece9eb89 ("Provide better cross references for namespace concepts")
Signed-off-by: Stephen Kitt <steve@sk2.org>
---
 sys-utils/nsenter.1 | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/sys-utils/nsenter.1 b/sys-utils/nsenter.1
index 9cce839c0..c51d9b04a 100644
--- a/sys-utils/nsenter.1
+++ b/sys-utils/nsenter.1
@@ -61,17 +61,18 @@ flag in
 .B PID namespace
 Children will have a set of PID to process mappings separate from the
 .B nsenter
-process
+process.
+.B nsenter
+will fork by default if changing the PID namespace, so that the new program
+and its children share the same PID namespace and are visible to each other.
+If \fB\-\-no\-fork\fP is used, the new program will be exec'ed without forking.
 For further details, see
 .BR pid_namespaces (7)
 and
 the discussion of the
 .B CLONE_NEWPID
 flag in
-.B nsenter
-will fork by default if changing the PID namespace, so that the new program
-and its children share the same PID namespace and are visible to each other.
-If \fB\-\-no\-fork\fP is used, the new program will be exec'ed without forking.
+.BR clone (2).
 .TP
 .B user namespace
 The process will have a distinct set of UIDs, GIDs and capabilities.
-- 
2.20.1

Re: [PATCH] docs: nsenter(1): fix further details in PID namespace section

[Michael Kerrisk (man-pages)]

Looks good to me.

Reviewed-by: Michael Kerrisk <mtk.manpages@gmail.com>

On Thu, 23 Apr 2020 at 10:38, Stephen Kitt <steve@sk2.org> wrote:
>
> The "Further details" sentence in the PID namespace section got merged
> with the surrounding text; this patch moves it to the end, to match
> the other namespace sections, and adds the missing clone(2) reference.
>
> Fixes: 894efece9eb89 ("Provide better cross references for namespace concepts")
> Signed-off-by: Stephen Kitt <steve@sk2.org>
> ---
>  sys-utils/nsenter.1 | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/sys-utils/nsenter.1 b/sys-utils/nsenter.1
> index 9cce839c0..c51d9b04a 100644
> --- a/sys-utils/nsenter.1
> +++ b/sys-utils/nsenter.1
> @@ -61,17 +61,18 @@ flag in
>  .B PID namespace
>  Children will have a set of PID to process mappings separate from the
>  .B nsenter
> -process
> +process.
> +.B nsenter
> +will fork by default if changing the PID namespace, so that the new program
> +and its children share the same PID namespace and are visible to each other.
> +If \fB\-\-no\-fork\fP is used, the new program will be exec'ed without forking.
>  For further details, see
>  .BR pid_namespaces (7)
>  and
>  the discussion of the
>  .B CLONE_NEWPID
>  flag in
> -.B nsenter
> -will fork by default if changing the PID namespace, so that the new program
> -and its children share the same PID namespace and are visible to each other.
> -If \fB\-\-no\-fork\fP is used, the new program will be exec'ed without forking.
> +.BR clone (2).
>  .TP
>  .B user namespace
>  The process will have a distinct set of UIDs, GIDs and capabilities.
> --
> 2.20.1
>


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

Re: [PATCH] docs: nsenter(1): fix further details in PID namespace section

[Karel Zak]

On Thu, Apr 23, 2020 at 10:37:02AM +0200, Stephen Kitt wrote:
>  sys-utils/nsenter.1 | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)

Applied, thanks.


-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com