http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1650
------- Comment #3 from jeff.morriss@xxxxxxxxxxx 2007-10-05 20:04 GMT -------
When I was looking through how dumpcap works with Wireshark/tshark I wondered
if something like this would be possible or not.
The basic question is: how can dumpcap be sure, when moving to the next file in
a ring buffer (and especially when deleting an old ringbuffer file), that
Wireshark is currently working on the same file dumpcap is. In other words,
it's possible that dumpcap could advance through several files before Wireshark
has finished processing the first one. In a ring-buffer situation (such as
this bug) dumpcap could erase, say, the 2nd generated file before Wireshark
gets to it. When Wireshark *does* get to it, you get the quoted error. Of
course this would only happen at high data rates or if Wireshark is really slow
(busy doing DNS lookups, for example).
Not sure what to do about that...
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.