Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] explicitly stop capture with Tshark

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: "Joshua (Shiwei) Zhao" <swzhao@xxxxxxxxx>
Date: Wed, 4 Feb 2009 18:50:36 -0800



 
That depends on how it's killed.

On UN*X, sending it SIGTERM, with, for example, the "kill" command,
will cause it to cleanly exit, flushing out the buffered packets.
Sending it a SIGINT by, for example, typing ^C to it while it's
running in the foreground will also cause it to cleanly exit.
 
However, by our previous experience with Ethereal, the "kill" command can only cleanly stop tshark sometimes. Many other times the packets were not correctly flushed out.
So this has been improved in Wireshark over Ethereal?
 
 
 
 

On Windows, currently the only way to get it to cleanly exit is to
send it a "control-C event"; I don't know whether there's any way to
do that other than to type ^C to it while it's running.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

  • Follow-Ups:
    • Re: [Wireshark-dev] explicitly stop capture with Tshark
      • From: Guy Harris
  • References:
    • [Wireshark-dev] explicitly stop capture with Tshark
      • From: Joshua (Shiwei) Zhao
    • Re: [Wireshark-dev] explicitly stop capture with Tshark
      • From: Guy Harris
  • Prev by Date: Re: [Wireshark-dev] Runtime error after a few hours of running
  • Next by Date: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86
  • Previous by thread: Re: [Wireshark-dev] explicitly stop capture with Tshark
  • Next by thread: Re: [Wireshark-dev] explicitly stop capture with Tshark
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation