namespaces.7: Fixes to text on forking a process into a PID namespace with no "init"

Based on comments from Eric Biederman

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2013-01-22 08:56:46 +01:00
parent bcf8010e24
commit 3c96796395
1 changed files with 8 additions and 9 deletions

View File

@ -334,18 +334,17 @@ If the "init" process of a PID namespace terminates,
the kernel terminates all of the processes in the namespace.
This behavior reflects the fact that the "init" process
is essential for the correct operation of a PID namespace.
In this case,
if another process holds an open file descriptor for one of the
.I /proc/[pid]/ns/pid
files for one of the processes that was in the namespace,
then a
.BR setns (2)
using that file descriptor will succeed, but a subsequent
In this case, a subsequent
.BR fork (2)
into this PID namespace (e.g., from a process that has done a
.BR setns (2)
into the namespace using an open file descriptor for a
.I /proc/[pid]/ns/pid
file corresponding to a process that was in the namespace)
will fail with the error
.BR ENOMEM ;
it is not possible to create a new processes in a PID namespace that has
no "init" process.
it is not possible to create a new processes in a PID namespace whose "init"
process has terminated.
Only signals for which the "init" process has established a signal handler
can be sent to the "init" process by other members of the PID namespace.