summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLucian Adrian Grijincu <lucian.grijincu@gmail.com>2010-10-30 07:52:36 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2010-10-30 07:52:36 +0200
commit61f22790e161346b309b2b0e12eb4ec771155f98 (patch)
treebb705e64c2219c1a8c67ed89e26c559041f384f5
parent52e27aeb24d87d47bed893180dfc50bd6853ad46 (diff)
unshare.2: Improve description of CLONE_NEWNET
CLONE_NEWNET creates a new network namespace from scratch. You don't have anything from the old network namespace in the new one. Even the loopback device is new. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man2/unshare.27
1 files changed, 4 insertions, 3 deletions
diff --git a/man2/unshare.2 b/man2/unshare.2
index db2e3536..27df76fd 100644
--- a/man2/unshare.2
+++ b/man2/unshare.2
@@ -14,7 +14,7 @@
.\" by clone, which would require porting and maintaining all commands
.\" such as login, and su, that establish a user session.
.\"
-.TH UNSHARE 2 2010-10-24 "Linux" "Linux Programmer's Manual"
+.TH UNSHARE 2 2010-10-30 "Linux" "Linux Programmer's Manual"
.SH NAME
unshare \- disassociate parts of the process execution context
.SH SYNOPSIS
@@ -95,8 +95,9 @@ This flag has the same effect as the
.B CLONE_NEWNET
flag.
Unshare the network namespace,
-so that the calling process has a private copy of the
-network namespace which is not shared with any other process.
+so that the calling process is moved into a
+new network namespace which is not shared
+with any previously existing process.
.BR CLONE_NEWNET
requires the
.BR CAP_SYS_ADMIN