From: Vadim Kochan <vadim4j@gmail•com>
To: Ben Hutchings <ben@decadent•org.uk>
Cc: Vadim Kochan <vadim4j@gmail•com>, netdev@vger•kernel.org
Subject: Re: [PATCH iproute2] man ip-netns: Fix syntax in default ns process, indent's
Date: Sat, 21 Mar 2015 13:46:41 +0200 [thread overview]
Message-ID: <20150321114641.GA31471@angus-think.lan> (raw)
In-Reply-To: <1426935263.32382.33.camel@decadent.org.uk>
On Sat, Mar 21, 2015 at 10:54:23AM +0000, Ben Hutchings wrote:
> On Sat, 2015-03-21 at 07:32 +0200, Vadim Kochan wrote:
> > From: Vadim Kochan <vadim4j@gmail•com>
> >
> > Signed-off-by: Vadim Kochan <vadim4j@gmail•com>
> > ---
> > man/man8/ip-netns.8 | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/man/man8/ip-netns.8 b/man/man8/ip-netns.8
> > index d496675..fe885db 100644
> > --- a/man/man8/ip-netns.8
> > +++ b/man/man8/ip-netns.8
> > @@ -46,7 +46,7 @@ ip-netns \- process network namespace management
> > A network namespace is logically another copy of the network stack,
> > with its own routes, firewall rules, and network devices.
> >
> > -By default process inherits network namespace from its parent. Initially all
> > +By default a process inherits network namespace from its parent. Initially all
> > the processes share the same default network namespace from the init process.
> >
> > By convention a named network namespace is an object at
> > @@ -103,10 +103,12 @@ option was specified then all the network namespace names will be removed.
> > It is possible to lose the physical device when it was moved to netns and
> > then this netns was deleted with a running process:
> >
> > +.RS
> > $ ip netns add net0
> > $ ip link set dev eth0 netns net0
> > $ ip netns exec net0 SOME_PROCESS_IN_BACKGROUND
> > $ ip netns del net0
> > +.RE
>
> You should delete the leading spaces as well.
>
> Ben.
>
> > and eth0 will appear in the default netns only after SOME_PROCESS_IN_BACKGROUND
> > will exit or will be killed. To prevent this the processes running in net0
>
> --
> Ben Hutchings
> If you seem to know what you are doing, you'll be given more to do.
Hi,
Would it be OK?
.RS 10
$ ip netns add net0
.RE
.RS 10
$ ip link set dev eth0 netns net0
.RE
.RS 10
$ ip netns exec net0 SOME_PROCESS_IN_BACKGROUND
.RE
.RS 10
$ ip netns del net0
.RE
Thanks,
prev parent reply other threads:[~2015-03-21 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 5:32 [PATCH iproute2] man ip-netns: Fix syntax in default ns process, indent's Vadim Kochan
2015-03-21 10:54 ` Ben Hutchings
2015-03-21 11:46 ` Vadim Kochan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150321114641.GA31471@angus-think.lan \
--to=vadim4j@gmail$(echo .)com \
--cc=ben@decadent$(echo .)org.uk \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox