http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1338
------- Comment #2 from sake@xxxxxxxxxx 2007-11-29 19:25 GMT -------
There have been significant changes to the capturing mechanism in tshark, could
you try a recent SVN to verify whether this problem still exists?
I tried the following myself:
ssh [email protected] /home/sake/wireshark/trunk/tshark -nl not port 22
After receiving some data, I pressed ctrl-c and looked at the process list on
192.168.1.5, no tshark process was running anymore, so to me it seems to work
correctly now.
Cheers, Sake
--
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.