https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16783
--- Comment #3 from Jim Aragon <j...@agdatasystems.com> ---
(In reply to Jaap Keuter from comment #2)
> Can you test with tshark as well? This would give an better idea if this
> issue is with the parameter handling, or the Qt UI. Either way I doubt this
> is dumpcap which has an issue.
I tested with tshark using the following command:
tshark -i 7 -w Bugzilla.pcapng -b duration:60
...where "7" is the interface index number of the active wireless adapter on
the laptop I was using for testing. I executed the command at time xx:xx:50 (10
seconds before the next even minute) several times. The problem did NOT occur,
and each time, tshark wrote the file--including the first one--for a full 60
seconds before rolling over to the next file.
Feel free to change the component from Dumpcap to whatever you think is more
appropriate. I really wasn't sure what to pick.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
