* parsing ethtool output in programs/scripts
@ 2015-09-02 0:22 Robert Urban
2015-09-02 0:33 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Robert Urban @ 2015-09-02 0:22 UTC (permalink / raw)
To: bwh, netdev
Hello,
I wish you would consider adding a switch to ethtool (and the corresponding
functionality) to produce output in machine-readable format.
This would be *extremely* useful.
Why not add the "--machine-readable" switch mentioned here:
http://www.hezmatt.org/~mpalmer/blog/2011/12/17/rethtool-how-i-learned-to-stop-worrying-and-love-the-ioctl.html
and another page which talks about the difficulty of parsing ethtool's output:
http://pjrlost.blogspot.de/2011/11/linuxunix-and-new-output-pipe-stdobj.html
cheers,
Robert Urban
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: parsing ethtool output in programs/scripts
2015-09-02 0:22 parsing ethtool output in programs/scripts Robert Urban
@ 2015-09-02 0:33 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2015-09-02 0:33 UTC (permalink / raw)
To: Robert Urban; +Cc: bwh, netdev
On Wed, 2 Sep 2015 02:22:18 +0200
Robert Urban <urban@unix-beratung.de> wrote:
> Hello,
>
> I wish you would consider adding a switch to ethtool (and the corresponding
> functionality) to produce output in machine-readable format.
>
> This would be *extremely* useful.
>
> Why not add the "--machine-readable" switch mentioned here:
Why not use json and --json flag like iproute2 tools are getting (gradually).
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-09-02 0:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-02 0:22 parsing ethtool output in programs/scripts Robert Urban
2015-09-02 0:33 ` Stephen Hemminger
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).