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: Jason House <jhouse@xxxxxxxxx>
Date: Mon, 01 Mar 2004 10:04:28 -0500
"Lars Ruoff" Wrote:

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

Both approaches (I believe) would separate "Capture Files" from "Capture Limits"... I think Biot's comments was just the "Capture Files" section. After looking at the merged version, I see there was already a maximum number of files in the capture limits section. How about something like the following? (I'm unsure if the details of a ring buffer should be in a tool tip or if there should be extra info in parenthesis following it)


---Capture file(s)---------------------------------------------
File: ___________________ Browse
O Write to multiple capture files
 O Next capture file every 1000___ kilobyte(s)
 O Next capture file every 300____ second(s)
 O Maximum number of files 2______
  O Ring Buffer
---------------------------------------------------------------
---Capture limit(s)---------------------------------------------
O Stop capture after 1______ packet(s)
O Stop capture after 1______ kilobyte(s)
O Stop capture after 1______ second(s)
---------------------------------------------------------------