Wireshark · Ethereal-dev: RE: [Ethereal-dev] Decoding packets while writing to file with te thereal

["Eichert, Diana" <deicher@xxxxxxxxxx>]

> -----Original Message-----
> From: Guy Harris [mailto:gharris@xxxxxxxxx]
> Sent: August 20, 2002 1:44 PM
> To: Joerg Mayer
> Cc: ethereal-dev@xxxxxxxxxxxx
> Subject: Re: [Ethereal-dev] Decoding packets while writing to 
> file with tethereal
> 
> On Tue, Aug 20, 2002 at 06:32:54PM +0200, Joerg Mayer wrote:
SNIP
> > Current behaviour (including my patch):
> > 
> > Option(s)	Action
> > none		capture and decode to stdout
> > -w file		capture to file, print number of packets to stderr
> > -q -w file	capture to file
> > -Q -w file	capture to file and decode to stdout   <--new
> > 
> > I'd prefer something like the following, because the behaviour of
> > printing a packet is not influenced by whether it is being 
> > written to file.
> > 
> > none		capture and decode to stdout
> > -w file		capture to file and decode to stdout
> > -q -w file	capture to file, print number of packets to stderr
> 
> Unfortunately, those change the behavior even when you're not using
> "-Q"; people might expect "-w" not to decode to stdout, and 
> might expect "-q" with "-w" not to write anything to stdout, and
> might even have scripts that assume that.

Hi

As the person who contributed the "-q" switch I think tethereal needs 
the ability to write nothing to stdout when capturing.  If you try to 
capture packets on a Gig interface you'll see where the overhead of 
writing to stdout effects the reliability of the capture, specifically 
in the number of dropped packets.

diana eichert