And you aren't giving me much to work with.

However, let's look at retransmissons for a second. Just like I taught myself how to translate or search for what information I need in the output of the command I am going to do the same for Perl: 

:
: some handwaving...
:
open PIPE,"netstat -s |" or die $!;
my @slurp=<PIPE>;
close PIPE;
chomp @slurp;
grep /Retran/,@slurp;
printf "%s\n",join("\n",@slurp);
:
:

[download]
is going to yeild me something like: 
    TCPLostRetransmit: 0
    TCPFastRetrans: 0
    TCPForwardRetrans: 0
    TCPSlowStartRetrans: 0

[download]

What you do beyond that depends on your requirements. I recommend you sit down and develop your requirements thoroughly and then plan your attack rather than fit your requirements to your attack. :-)

I hope this isn't homework!

In reply to Re: Re: Re: Netstat summary and Perl? by blue_cowdawg
in thread Netstat summary and Perl? by u235sentinel

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.