Actually, pktt does continue tracing into the memory buffer, but it stops writing to a trace file once the -s limit is hit. And there are limits on the size of the internal (-b) buffers available for pktt (around 64MB total).
At the moment pktt does not have a way to automatically keep a rotating log of trace files. However, this can be done with a perl script, for example. The basic idea would be to trace to files using the -d option, then periodically stop tracing, delete the oldest trace file, rename the trace files as needed to keep the desired amount of data in the rotating log, then start tracing again.
Mark
-----Original Message----- From: Stephane Bentebba [mailto:stephane.bentebba@fps.fr] Sent: Wednesday, October 01, 2003 1:55 AM Cc: 'toasters@mathworks.com' Subject: Re: Wrapping pktt trace?
pktt won't stop to trace when it reach the limit pktt do record in a cycle fashion
use this command to pktt start e0 -s 500M to save a trace to a file of 500MB max check this link for all details about the syntax
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=4.0.852643.25153 26&resource= if your Filer has enought memory and is powerfull enought, you can consider to use the -b option which use the memory as the temporary file
: this way you are sure to get ALL packets going throught the interface
Edward Hibbert (eh@dataconnection.com) wrote:
To catch an application problem, I want to leave pktt trace running on
a
filer...overnight. If I do, it'll fill it up.
I know you can tell it to bound the amount of space it uses, but I
think it
stops tracing once it hits that. Is there any way to get it to keep
tracing
within a bounded amount of disk space, just overwriting old trace
files?
That way I would have the last few hours of trace.
Thanks,
Edward Hibbert Internet Applications Group Data Connection Ltd Tel: +44 131 662 1212 Fax: +44 131 662 1345 Email: eh@dataconnection.com Web: http://www.dataconnection.com