Message-Id: <200102222139.QAA12787@picard.cs.ohiou.edu> From: "Shawn Ostermann" <ostermann@cs.ohiou.edu> Subject: Re: problem of memory with tcptrace Date: Thu, 22 Feb 2001 16:39:44 -0500
>> i have done what you said and it's a problem of swap, when there is only 60
>> Mo of swap tcptrace stop
Yes, according to the file you sent, the problem is exactly as I said,
you're out of swap space. Looking at the memory requested on the
heap, it looks like you're pushing up into a heap size of 1.8 GB for
this program. If you're not "almost done" with the file at that
point, then you're going to have to split the file up to process it,
because I suspect that you're next going to run up against the total
virtual memory limit. If you run tcptrace with the -t option, it'll
tell you it's progress in packets and wallclock time, which should
give you some idea how close it is to being done (if you know the
timeframe that the file represents).
If you need to break up the file, you should look into 'tcpslice',
which is very handy for splitting files into pieces.
--sdo
This archive was generated by hypermail 2b30 : 02/23/01 EST