From 25539b1b6ca3ce29ec035f98380464bf10dbfe29 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sun, 24 Oct 2010 16:14:09 +0200 Subject: [PATCH] unshare.2: Document CLONE_NEWIPC Signed-off-by: Michael Kerrisk --- man2/unshare.2 | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/man2/unshare.2 b/man2/unshare.2 index afbfeec39..b056af1c6 100644 --- a/man2/unshare.2 +++ b/man2/unshare.2 @@ -14,7 +14,6 @@ .\" by clone, which would require porting and maintaining all commands .\" such as login, and su, that establish a user session. .\" -.\" FIXME Document CLONE_NEWIPC, which is new in 2.6.18 .\" FIXME Document CLONE_NEWUTS, which is new in 2.6.19 .\" FIXME Document CLONE_SYSVSEM, which is new in 2.6.26 .\" @@ -76,6 +75,23 @@ or umask attributes with any other process. or .BR umask (2) .TP +.BR CLONE_NEWIPC " (since Linux 2.6.19) +This flag has the same effect as the +.BR clone (2) +.B CLONE_NEWIPC +flag. +Unshare the System V IPC namespace, +so that the calling process has a private copy of the +System V IPC namespace which is not shared with any other process. +Specifying this flag automatically implies +.BR CLONE_SYSVSEM +as well. +Use of +.BR CLONE_NEWIPC +requires the +.BR CAP_SYS_ADMIN +capability. +.TP .B CLONE_NEWNS .\" These flag name are inconsistent: .\" CLONE_NEWNS does the same thing in clone(), but CLONE_VM,