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: 894efece9e
("Provide better cross references for namespace concepts")
Signed-off-by: Stephen Kitt <steve@sk2.org>
This commit is contained in:
parent
243fff1dc6
commit
32ff1494e3
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue