Fellow Monks, I come to you with a question over a few things. First of course is perl versus another solution (basic shell) and the next is over libpcap and tcpdump. I currently have a script (shell) that looks something like this snidbit:
#!/bin/sh # # # Sector au-135 cd /tmp/tcptrace FILENAME=au135-`date +%Y%m%d%H%M%S`.tcpdump /usr/sbin/tcpdump -n -c 30000 -w /tmp/tcptrace/$FILENAME -i eth1 host +`/usr/local/bin/which-hosts au-135 50|/usr/local/bin/host-it.pl`& MYJOB=$! sleep 60 sync kill $MYJOB /usr/local/bin/tcptrace-munch $FILENAME rm /tmp/tcptrace/$FILENAME
Basically I am going to be going back to tcpdump to dump data for a certain "sector" of users on a broadband network. With shell, I am using sleep, and doing these all at once. I am planning on updating to perl with systems calls and forking off multiple tcpdump sessions at once, but I wanted to ask if anyone had done something like this before. Will tcpdump run multiple sessions? What type of load are we talking if somewhere around 15 sessions are running? What type of degredation of integrity/is there any that I can expect from the data recieved through tcpdump? Thanks ahead of time for any help you can spare.

Tradez
"Never underestimate the predicability of stupidity"
- Bullet Tooth Tony, Snatch (2001)

In reply to To Shell or To Perl, that is the question by tradez

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.