Wireshark-bugs: [Wireshark-bugs] [Bug 1495] New: multiple files creates a ton of empty 1 or 2 K

Date: Tue, 27 Mar 2007 19:53:23 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1495

           Summary: multiple files creates a ton of empty 1 or  2 K files
           Product: Wireshark
           Version: 0.99.5
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: tlange@xxxxxxx


Build Information:
Version 0.99.5 (SVN Rev 20677)

Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 GTK+ 2.10.7, with GLib 2.12.7, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1,
with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio
PortAudio V19-devel, with AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0
(packet.dll version 4.0.0.755), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
I set up the product to capture named files (multiple files) of 2m each to a
ring buffer of 2400 files. I need to monitor a user all day long until a
particular problem happens then go look for packets in and around that time
frame.  If is set to a small number of files...4 or 5, it works.  If I set to a
large number of files then what I get is one file, the first one, of the
correct size limit, the rest are all 1 and 2 K files with nothing or maybe one
packet in them.    What's weird is that the entire time that wireshark is
running I can have that directory where the files are being stored open in
windows explorer and do refreshes periodically and they all look fine, each one
the size they should be before the file is closed and a new one created.  It
isn't until I stop the capture and then try to go open them that this file size
anomoly becomes appearant.


-- 
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.