Launchpad has imported 9 comments from the remote bug at http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2743.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-07-25T10:37:46+00:00 Guy Harris wrote: Build Information: TShark 1.0.2 (SVN Rev 25698) Copyright 1998-2008 Gerald Combs <ger...@wireshark.org> and contributors. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled with GLib 2.16.3, with libpcap 0.9.5, with libz 1.2.3, without POSIX capabilities, without libpcre, without SMI, without ADNS, without Lua, without GnuTLS, without Gcrypt, with MIT Kerberos. NOTE: this build doesn't support the "matches" operator for Wireshark filter syntax. Running on Darwin 9.4.0 (MacOS 10.5.4), with libpcap version 0.9.5. Built using gcc 4.0.1 (Apple Inc. build 5465). -- TShark, when run without -w, isn't told to permanently save the captured packets to a file; it's only supposed to dissect and print the packets. Currently, it does that by running dumpcap without "-w", so that it writes to a temporary file, and then reads the temporary file. This means that if you leave TShark running for a long period of time, and it captures a lot of packets, a large capture file is written, which can fill up the disk; In addition, it appears that, in some cases, the capture file isn't deleted. TShark should run dumpcap in a mode where it writes the captured packets to a pipe, fflushing the output stream at the end of a packet batch, and reads captured packets from the pipe. Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/1 ------------------------------------------------------------------------ On 2008-10-01T04:02:00+00:00 Rtarty wrote: Created attachment 2290 Script to reorder TCP streams. Last version of Scapy requiried. Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/2 ------------------------------------------------------------------------ On 2008-10-01T06:19:07+00:00 Jeff-morriss-ws wrote: Comment on attachment 2290 Script to reorder TCP streams. This attachment was meant for bug 2722. Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/3 ------------------------------------------------------------------------ On 2009-01-08T08:01:58+00:00 Jeff-morriss-ws wrote: Bug 1650 (error when using ring buffer mode when the buffer files are deleted before *shark gets to them) could also benefit from using a pipe to pass packets from dumpcap to *shark. (Doing that would also allow read filters to work while capturing again.) Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/6 ------------------------------------------------------------------------ On 2009-07-23T05:07:24+00:00 Balint Reczey wrote: The problem of not removing temporary capture file is reported to Debian BTS, too: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518904 I've set the bug in Debian BTS to track this bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/8 ------------------------------------------------------------------------ On 2011-11-21T18:35:57+00:00 Guy Harris wrote: *** Bug 6604 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/12 ------------------------------------------------------------------------ On 2013-10-11T04:15:15+00:00 Hoangsonvnu wrote: > TShark should run dumpcap in a mode where it writes the captured packets to a > pipe, fflushing the output stream at the end of a packet batch, and reads > captured packets from the pipe @Jeff Morriss: Has this suggestion been done in tshark of the branch trunk-1.10? If we do this, does it mean we don't need a temp .pcap file stored in the disk and the data could be transferred directly from dumpcap to tshark via a pipe? Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/17 ------------------------------------------------------------------------ On 2013-10-11T06:16:03+00:00 Guy Harris wrote: (In reply to comment #6) > > TShark should run dumpcap in a mode where it writes the captured packets to > > a > > pipe, fflushing the output stream at the end of a packet batch, and reads > > captured packets from the pipe > > @Jeff Morriss: Has this suggestion been done in tshark of the branch > trunk-1.10? As one might infer from the fact that this bug is in the CONFIRMED state rather than the RESOLVED/FIXED state, this has not been done anywhere in the SVN repository for Wireshark. Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/18 ------------------------------------------------------------------------ On 2019-01-05T08:38:09+00:00 Rossbjacobs wrote: *** Bug 15298 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/210670/comments/19 ** Changed in: wireshark Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/210670 Title: tshark uses up all the space in /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/wireshark/+bug/210670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
