On 11/27/2013 10:24 PM, Maynard, Chris wrote:
> I believe you are looking at the output after tshark has been run twice, once with each set of arguments. When it runs with the first set of args, you will see:
>
> Pass 1:
> arp: (-nVxr)
>
> ... and when it runs with the second set of args, you will see:
>
> Pass 1:
> arp: (-nVxr) (-nr)
>
> After that completes, you'll see:
>
> Pass 1:
> arp: (-nVxr) (-nr) OK
>
> ... and then on to the next one:
>
> Pass 1:
> arp: (-nVxr) (-nr) OK
> bgp: (-nVxr)
>
> etc.
>
Right - and I overlooked the "-n" for the echo command - sry for the noise
>
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Toralf Förster
> Sent: Wednesday, November 27, 2013 3:24 PM
> To: Developer support list for Wireshark
> Subject: [Wireshark-dev] q: why does ./tools/randpkt-test.sh uses a bash array for TSHARK_ARGS
>
> From what I can see there's just 1 call of tshark with all args at once, or ? And the output proves it too :
> (pls Cc: me directly)
>
>
>
> tfoerste@n22 ~ $ cd ~/devel/wireshark/; nice ./tools/randpkt-test.sh Running ./tshark with args: "-nVxr" "-nr" (forever) Running ./randpkt with args: -b 2000 -c 5000
>
> Pass 1:
> arp: (-nVxr) (-nr) OK
> bgp: (-nVxr) (-nr) OK
> bvlc: (-nVxr) (-nr) OK
> dns: (-nVxr) (-nr) OK
>
>
>
>
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3