Wireshark-bugs: [Wireshark-bugs] [Bug 6256] Running "wireshark -i <interface> -c 100 -k -Q -w -"
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6256
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
--- Comment #10 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2011-08-24 06:50:23 PDT ---
(In reply to comment #7)
> The reason why Wireshark quits rather than leaving the dialog up is the -Q
> flag, which means "quit as soon as the capture stops"; it's not clear that's a
> useful option for Wireshark, so the right way to handle that might be to nuke
> the -Q flag. (The person who discovered the crash probably had no use for the
> GUI and really wanted TShark.) I've asked on wireshark-users whether anybody
> has any use for -Q; if not, the right fix is to get rid of that option in the
> Wireshark code.
I think/imagine the only place that "-Q" gets used is in the test suite
(testing to see that we can capture with the GUI).
You (Guy) once proposed[1] using getopt_long() for "weird" options like this.
But if it is truly used only for the testsuite, maybe something backdoor-ish
like an environment variable would work.
[1] http://www.wireshark.org/lists/wireshark-users/200802/msg00208.html
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
