From: Stephen Hemminger <stephen@networkplumber.org>
To: roopa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, haegar@sdinet.de
Subject: Re: [PATCH iproute2] fix ip -force -batch to continue on errors
Date: Tue, 24 Mar 2015 15:00:21 -0700 [thread overview]
Message-ID: <20150324150021.1cf3a756@urahara> (raw)
In-Reply-To: <1426645592-4002-1-git-send-email-roopa@cumulusnetworks.com>
On Tue, 17 Mar 2015 19:26:32 -0700
roopa@cumulusnetworks.com wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This patch replaces exits with returns in several
> iproute2 commands. This fixes `ip -batch -force`
> to not exit but continue on errors.
>
> $cat c.txt
> route del 1.2.3.0/24 dev eth0
> route del 1.2.4.0/24 dev eth0
> route del 1.2.5.0/24 dev eth0
> route add 1.2.3.0/24 dev eth0
>
> $ip -force -batch c.txt
> RTNETLINK answers: No such process
> Command failed c.txt:2
> RTNETLINK answers: No such process
> Command failed c.txt:3
>
> Reported-by: Sven-Haegar Koch <haegar@sdinet.de>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Applied thanks
prev parent reply other threads:[~2015-03-24 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 2:26 [PATCH iproute2] fix ip -force -batch to continue on errors roopa
2015-03-19 17:58 ` Sven-Haegar Koch
2015-03-24 22:00 ` Stephen Hemminger [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=20150324150021.1cf3a756@urahara \
--to=stephen@networkplumber.org \
--cc=haegar@sdinet.de \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
/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