One other item: You don't really need the cat statement, as grep can read from the file just as easily as it can read from the pipe:

grep eth0 /proc/net/dev | awk '{print $2}' | sed 's/eth0://g'

[download]

then, of course, you really don't need the grep, either, as awk knows how to run a block only when it finds a regular expression:

awk '/eth0/ {print $2}' /proc/net/dev | sed 's/eth0://g'

[download]

After that, we don't really need the sed statement either, as awk can also do a regular expression substitution:

awk '/eth0/ {print gensub("eth0","","g",$2); }' /proc/net/dev'

[download]
Of course, since this is a perl site, you might just want to use perl...

...roboticus

In reply to Re: system command question by roboticus
in thread system command question by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.