parsing the output of ethtool programmatically

parsing the output of ethtool programmatically

[Robert Urban]

Hello,

there doesn't seem to be any flag to request ethtool to present its output in a
script-friendly form.  Things like:
>         Link partner advertised link modes:  10baseT/Half 10baseT/Full
>                                              100baseT/Half 100baseT/Full
>                                              1000baseT/Full
are kind of pain to parse.

Something to consider?

Robert Urban

Re: parsing the output of ethtool programmatically

[Ben Hutchings]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

On Thu, 2015-06-25 at 03:28 +0200, Robert Urban wrote:
> Hello,
> 
> there doesn't seem to be any flag to request ethtool to present its output in a
> script-friendly form.  Things like:
> >         Link partner advertised link modes:  10baseT/Half 10baseT/Full
> >                                              100baseT/Half 100baseT/Full
> >                                              1000baseT/Full
> are kind of pain to parse.
> 
> Something to consider?

Or write a library for using SIOCETHTOOL.  The interface is fairly well
documented now and there are other users besides the ethtool utility.

Ben.

-- 
Ben Hutchings
friends: People who know you well, but like you anyway.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

Re: parsing the output of ethtool programmatically

[roopa]

On 9/5/15, 2:53 AM, Ben Hutchings wrote:
> On Thu, 2015-06-25 at 03:28 +0200, Robert Urban wrote:
>> Hello,
>>
>> there doesn't seem to be any flag to request ethtool to present its output in a
>> script-friendly form.  Things like:
>>>          Link partner advertised link modes:  10baseT/Half 10baseT/Full
>>>                                               100baseT/Half 100baseT/Full
>>>                                               1000baseT/Full
>> are kind of pain to parse.
>>
>> Something to consider?
> Or write a library for using SIOCETHTOOL.  The interface is fairly well
> documented now and there are other users besides the ethtool utility.

one of the requests which we usually get is ethtool output in json 
format. since iproute2 tools are already getting
an option to print in json format, would be nice if we considered an 
option to print in json for ethtool too.

Re: parsing the output of ethtool programmatically

[Robert Urban]

may I also suggest being able to specify the offload parameters in the format in
which "ethtool -k <nic>" prints them? The user can only guess which -K
parameters correspond to the -k parameters.


On 09/08/2015 04:52 AM, roopa wrote:
> On 9/5/15, 2:53 AM, Ben Hutchings wrote:
>> On Thu, 2015-06-25 at 03:28 +0200, Robert Urban wrote:
>>> Hello,
>>>
>>> there doesn't seem to be any flag to request ethtool to present its output in a
>>> script-friendly form.  Things like:
>>>>          Link partner advertised link modes:  10baseT/Half 10baseT/Full
>>>>                                               100baseT/Half 100baseT/Full
>>>>                                               1000baseT/Full
>>> are kind of pain to parse.
>>>
>>> Something to consider?
>> Or write a library for using SIOCETHTOOL.  The interface is fairly well
>> documented now and there are other users besides the ethtool utility.
>
> one of the requests which we usually get is ethtool output in json format.
> since iproute2 tools are already getting
> an option to print in json format, would be nice if we considered an option to
> print in json for ethtool too.
>
>