Package: tshark Version: 1.0.6-1 Severity: normal File: /usr/bin/tshark Recent versions of tshark call dumpcap internally as a coprocess and communicate captured packets via a temporary uniquely named file /tmp/etherXXXXXXXXXX. However, tshark fails to remove this file when it exits, littering /tmp with capture files.
Unless tshark is called with -w to save the captured packets to a specific location, I think it could behave better by cleaning up after itself. (This was the behavior up until approximately v0.99.7 after which the dumpcap coprocess was introduced.) -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tshark depends on: ii libadns1 1.4-2 Asynchronous-capable DNS client li ii libc6 2.7-18 GNU C Library: Shared libraries ii libcomerr2 1.41.3-1 common error description library ii libgcrypt11 1.4.1-1 LGPL Crypto library - runtime libr ii libglib2.0-0 2.16.6-1 The GLib library of C routines ii libgnutls26 2.4.2-6+lenny1 the GNU TLS library - runtime libr ii libkrb53 1.6.dfsg.4~beta1-5 MIT Kerberos runtime libraries ii libpcap0.8 0.9.8-5 system interface for user-level pa ii libpcre3 7.8-2 Perl 5 Compatible Regular Expressi ii wireshark-common 1.0.6-1 network traffic analyser (common f ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime tshark recommends no packages. tshark suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
