Manual pages: unshare.1: clarify that --pid=<file> requires --fork

Attempting to create a persistent PID namespace with --pid=<file>
will result in an error if --fork is not also specified. Let's
warn people about that, so they don't get puzzled.

Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
Signed-off-by: Karel Zak <kzak@redhat.com>
This commit is contained in:
Michael Kerrisk (man-pages) 2020-06-03 09:40:57 +02:00 committed by Karel Zak
parent 48994386a1
commit 4d4f56baad
1 changed files with 7 additions and 2 deletions

View File

@ -114,8 +114,13 @@ Unshare the network namespace. If \fIfile\fP is specified, then a persistent
namespace is created by a bind mount.
.TP
.BR \-p , " \-\-pid" [ =\fIfile ]
Unshare the PID namespace. If \fIfile\fP is specified then persistent
namespace is created by a bind mount. See also the \fB\-\-fork\fP and
Unshare the PID namespace. If \fIfile\fP is specified, then a persistent
namespace is created by a bind mount.
(Creation of a persistent PID namespace will fail if the
.B \-\-fork
option is not also specified.)
.IP
See also the \fB\-\-fork\fP and
\fB\-\-mount-proc\fP options.
.TP
.BR \-u , " \-\-uts" [ =\fIfile ]