[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20151103233552.GB26876@orbit.nwl.cc>
Date: Wed, 4 Nov 2015 00:35:52 +0100
From: Phil Sutter <phil@....cc>
To: Stephen Hemminger <shemming@...cade.com>
Cc: netdev@...r.kernel.org,
Petr Písař <ppisar@...hat.com>
Subject: Re: [iproute PATCH] Confirm success for each tc -batch command
On Tue, Nov 03, 2015 at 12:46:21PM -0800, Stephen Hemminger wrote:
> On Thu, 29 Oct 2015 13:09:56 +0100
> Phil Sutter <phil@....cc> wrote:
>
> > If `tc -force -batch' is fed by a controlling program from a pipe,
> > it's not possible to recognize when a command has been processes
> > successfully.
> >
> > This patch adds an optional `-OK' option to the tc(8) tool, so `tc
> > -force -OK -batch' will print "OK\n" to standard output on each
> > successfully completed tc command.
> >
> > Signed-off-by: Petr Písař <ppisar@...hat.com>
> > Signed-off-by: Phil Sutter <phil@....cc>
>
> Why use batch mode if you are feeding it from a pipe?
> This seems like unnecessary feature creep.
This turned up when searching the list of iproute2 patches in RHEL6 for
unpublished changes. It dates back to a feature request from 2012 by a
customer who wanted to know when a command piped into tc was finished
processing. Looking at the ticket again, it appears you rejected this
patch in 2013 already. So I guess everything has been said but "sorry
for the noise"!
Cheers, Phil
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists