cga2000 wrote:
On Tue, Dec 18, 2007 at 09:57:44PM EST, Matthew Woehlke wrote:
You might want to look at bash's command redirection instead.
?
Sorry, the "correct" term (at least, what the manpage uses :-) ) is
"process substitution". Conceptually, it's a bit like writing pipes
backwards. F
On Tue, Dec 18, 2007 at 09:57:44PM EST, Matthew Woehlke wrote:
> cga2000 wrote:
> >I was wondering if there is any way I can convince netstat to return
> >its output to bash variables for processing.
> >
> >Pretty simple logic:
> >
> >Do forever:
> >
> > Call netstat to obtain RX & TX byte counts
cga2000 wrote:
I was wondering if there is any way I can convince netstat to return
its output to bash variables for processing.
Pretty simple logic:
Do forever:
Call netstat to obtain RX & TX byte counts
Print delta {current .. minus previous .. byte counts}
Save current byte counts
I was wondering if there is any way I can convince netstat to return
its output to bash variables for processing.
Pretty simple logic:
Do forever:
Call netstat to obtain RX & TX byte counts
Print delta {current .. minus previous .. byte counts}
Save current byte counts
Wait for a secon
