From: Jose Manuel Cano Garcia (cano@dte.uma.es)
Date: 02/18/05
Message-ID: <42160A92.8090606@dte.uma.es> Date: Fri, 18 Feb 2005 16:32:34 +0100 From: Jose Manuel Cano Garcia <cano@dte.uma.es> Subject: Re: problems with tcptrace
I have had memory problems (and my computer has 1 GB of physical memory)
when processing traces with many connections because it seems that
tcptrace allocates memory for each connection it processes, and does not
dump the results (and deallocate the memory) until the end of the
process. Therefore, it may run out of memory for big trace files. To
solve the problem I have to split the trace in several files by
preprocessing them with tcpdump (using a random criteria that clasified
all packets of the same connection in the same destination file such as
the destination/source port, range of source/destination IP adrresses,
etc.). Long ago, I sent to the mailing several scripts to that. If you
need them but could not find them, please let me know and I will send to
you.
hela boucetta wrote:
>I used tcptrace to get long format output from dump traces.I have traces for different times a day, for many days. when processing tcptrace on dump files it stops and do not print results for some files -during the same periods for all the days. it stops after doing 40%, 45%, 25% ;some times after 80% or 95% (I used the -t option to visualize the feedback of tcptrace progress). the size of these files exceeds 60Mb and probably it corresponds to the moments when there is a lot of traffic in the network.
>
>I have not problems with the performances of the machine on wich I am proceesing analysis ( memory 512 MB, 120GB capacity of the harddisk).
>
>I would be very pleased if you can tell me why tcptrace stops without generating results?
>any help will be appreciated.
>
>___________________________________________________
>Share diaries and photos with your friends and family.
>
>http://www.homemaster.net - Homemaster. Come Together. Online.
>
>----------------------------------------------------------------------------
>To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
>majordomo@tcptrace.org.
>
>.
>
>
>
----------------------------------------------------------------------------
To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
majordomo@tcptrace.org.
This archive was generated by hypermail 2.1.7 : 02/18/05 EST