Wireshark · Ethereal-dev: Re: [Ethereal-dev] Capture dialog ringbuffer behaviour

[John McDermott <jjm@xxxxxxxxxx>]

Ulf Lamping wrote:
e case is that they want to run a capture for a very
> > long time, but not to have a single giant capture file - they want the
> > file carved into smaller pieces, to cut the amount of data in a single
> > file and thus to make it less painful to, for example, process the file
> > in Ethereal.
> >
> >  
> I see this use case and I sometimes need this.
>
> But that's an explanation for the ring buffer (or multiple files) 
> feature, but that's no explanation for *infinite* ring buffer files.

I think the case can also be made for "I don't know how many files to 
make so just make them until I stop it".  That is not really "infinite", 
but "not known in advance".  I can see myself using this more than the "I 
know how many files I need" version of "multiple files".

> >
> Sorry, I don't see these warnings.
>
> Maybe we need some sort of error log instead of the console output (at 
> least on win32).

Or a log to the application part of Event Viewer?

--john


--
John McDermott
Writer, Educator, Consultant
jjm@xxxxxxxxxx		http://www.jkintl.com
V +1 505/377-6293 F +1 505/377-6313