Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: Re: [Ethereal-dev] Capture ringbuffer behaviour, 2nd proposal

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Lars Ruoff" <lars.ruoff@xxxxxxxxxxxxxxxxxx>
Date: Mon, 1 Mar 2004 13:28:46 +0100
too complex/unintuitive IMO.
I prefer Ulf Lampings approach.
I like the clear split into "Capture Files" and "Capture Limits".
just my personal opinion of course,
Lars

----- Original Message ----- 
From: "Biot Olivier" <Olivier.Biot@xxxxxxxxxxx>
To: "'Ethereal development'" <ethereal-dev@xxxxxxxxxxxx>
Sent: Monday, March 01, 2004 11:49 AM
Subject: RE: [Ethereal-dev] Capture ringbuffer behaviour, 2nd proposal


> Hi list,
>
> What I see as functionality in the capture file logic, is:
>
> [a] Write to multiple capture files
>     (b1) Next capture file every __[1000] kilobyte(s)
>     (b2) Next capture file every ___[300] second(s)
>
>     [c] Maximum number of capture files: ____[2]
>         [d] Overwrite oldest capture files when maximum
>             number of capture files has been reached.
>
> If checkbox [a] is set, then radio button (b1) is selected by default and
> checkboxes [c] and [d] are not set. The default value for (b1) is 1000
> kbyte, the default value for (b2) is 300 seconds. If [c] is set, then the
> default number of files is 2. And [d] can only be set if [c] has been set,
> and this represents the "ring buffer" feature.
>
> Tooltip for [a]:
>     If enabled, Ethereal will write captured packets to
>     more than one file. You can specify when a new file
>     must be opened for writing.
>
> Tooltip for [c]:
>     If enabled, Ethereal will only produce up to the
>     specified number of capture files.
>
> Tooltip for [d]:
>     If enabled, Ethereal will rotate the capture files.
>     This allows to capture a limited amount of traffic
>     until a stop condition has been reached.
>
> Hope this helps!
>
> Regards,
>
> Olivier
>
> |-----Original Message-----
> |From: Guy Harris
> |
> |Lars Ruoff said:
> |> Sounds very good to me, except that you shouldnt normally
> |use the term
> |> "ring buffer" at all, if you dont come back to the first
> |file, do you?
> |
> |I agree (unless you choose to consider it a ring with an
> |infinite diameter
> |:-)).
> |
> |> Replace it by "Use multiple files"? and perhaps add the term
> |ring buffer
> |> to last entry?
> |> ---Capture file(s)---------------------------------------------
> |> File: ___________________ Browse
> |> O Use multiple files:
> |>  X Next capture file every 1______ kilobyte(s)
> |>  O Next capture file every 1______ second(s)
> |>  X Back to first file after 2______ files (Ring Buffer)
> |
> |That sounds reasonable, although "Use multiple files" appears to be
> |redundant - if neither of the "Next capture file every..." options is
> |selected, you're not using multiple files, otherwise you are.
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev