From: Vadim Kochan <vadim4j@gmail.com>
To: Cong Wang <cwang@twopensource.com>
Cc: Vadim Kochan <vadim4j@gmail.com>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2 0/3] ip netns: Run over all netns
Date: Thu, 8 Jan 2015 02:52:12 +0200 [thread overview]
Message-ID: <20150108005212.GA10487@angus-think.lan> (raw)
In-Reply-To: <CAHA+R7OpGoYx51DQfLhFiZmU_jMfd28G6kssgft6NQoFXj_X+A@mail.gmail.com>
On Wed, Jan 07, 2015 at 04:04:14PM -0800, Cong Wang wrote:
> On Wed, Jan 7, 2015 at 3:04 AM, Vadim Kochan <vadim4j@gmail.com> wrote:
> > From: Vadim Kochan <vadim4j@gmail.com>
> >
> > Allow 'ip netns del' and 'ip netns exec' run over each network namespace names.
> >
> > 'ip netns exec' executes command forcely on eacn nsname.
> >
>
> Why this has to be done in iproute command?
> That is, why not just offloading this to a shell script like below?
>
> for ns in `ip netns show`;
> do
> ip netns exec $ns ip link show.....
> done
Hm, but would not it better to have it in iproute instead of collect
scripts ? Scripts allows to do a lot of things, but in this case it seems like a
feature which related to iproute.
next prev parent reply other threads:[~2015-01-08 1:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 11:04 [PATCH iproute2 0/3] ip netns: Run over all netns Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 1/3] lib: Exec func on each netns Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 2/3] ip netns: Allow exec " Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 3/3] ip netns: Delete all netns Vadim Kochan
2015-01-07 15:44 ` Brian Haley
2015-01-07 17:36 ` Vadim Kochan
2015-01-07 18:11 ` Vadim Kochan
2015-01-07 19:40 ` Brian Haley
2015-01-07 19:55 ` Vadim Kochan
2015-01-08 0:00 ` Cong Wang
2015-01-09 8:43 ` Jiri Benc
2015-01-09 9:54 ` Vadim Kochan
2015-01-09 14:24 ` Nicolas Dichtel
2015-01-08 0:04 ` [PATCH iproute2 0/3] ip netns: Run over " Cong Wang
2015-01-08 0:52 ` Vadim Kochan [this message]
2015-01-09 18:49 ` Cong Wang
2015-01-09 19:17 ` Vadim Kochan
2015-01-14 1:28 ` Stephen Hemminger
2015-01-14 16:13 ` Vadim Kochan
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=20150108005212.GA10487@angus-think.lan \
--to=vadim4j@gmail.com \
--cc=cwang@twopensource.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).