diff options
author | Andre Luyer <andre@luyer.nl> | 2021-07-04 17:43:02 +0200 |
---|---|---|
committer | Guy Harris <gharris@sonic.net> | 2021-07-04 19:55:59 +0000 |
commit | 9f8e6b1acb83a74c9efda70f97b5fb9f1771d2b8 (patch) | |
tree | 2042bbec61ccb4063e25d4caa0862aebbcaf80dd /ui/commandline.c | |
parent | d170dff7ebfbdd4131679565e9c3c17ea797dd88 (diff) |
tshark/wireshark: Fix check ring buffer option for packets
tshark and wireshark did not allow only -b packets:value option, while dumpcap does.
This change adds the same check in tshark and wireshark as in dumpcap.
Quick fix for issue mentioned at https://ask.wireshark.org/question/23437/why-does-tshark-b-packetsvalue-not-work/
Diffstat (limited to 'ui/commandline.c')
-rw-r--r-- | ui/commandline.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/ui/commandline.c b/ui/commandline.c index ebfc5eae50..66a82493ab 100644 --- a/ui/commandline.c +++ b/ui/commandline.c @@ -685,8 +685,9 @@ void commandline_other_options(int argc, char *argv[], gboolean opt_reset) } if (!global_capture_opts.has_autostop_filesize && !global_capture_opts.has_file_duration && - !global_capture_opts.has_file_interval) { - cmdarg_err("Ring buffer requested, but no maximum capture file size, duration or interval were specified."); + !global_capture_opts.has_file_interval && + !global_capture_opts.has_file_packets) { + cmdarg_err("Ring buffer requested, but no maximum capture file size, duration, interval or packets were specified."); /* XXX - this must be redesigned as the conditions changed */ } } |