Skip to contentSkip to conversation

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

PATCH Applied Stephen Kitt 3 participants 3 messages Apr 23, 2020 – Apr 27, 2020 Util-Linux package

lore
Share & tools
lore
#0 lore raw

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

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")
---
 sys-utils/nsenter.1 | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)
sys-utils/nsenter.1 +6 -5
index 9cce839c0..c51d9b04a 100644
@@ -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.
Signature · 1 line
2.20.1
Reviewed-by on v1 1/1
#1 lore raw

Looks good to me.

Quoted 42 lines · 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")
---
 sys-utils/nsenter.1 | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)
sys-utils/nsenter.1 +6 -6
index 9cce839c0..c51d9b04a 100644
@@ -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

Signature · 3 lines
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
maintainer Applied
#2 lore raw
In reply to Stephen Kitt
Quoted 2 lines · Stephen Kitt
 sys-utils/nsenter.1 | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

Applied, thanks.

Signature · 2 lines
 Karel Zak  <[email protected]>
 http://karelzak.blogspot.com