Ethereal-dev: RE: [Ethereal-dev] Need Urgent Help - Maintenance of Tethereal state information

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Neulinger, Nathan" <nneul@xxxxxxx>
Date: Fri, 21 Feb 2003 08:38:58 -0600
Do you care about overlap of capture data? If not, you could probably
start the new capture 10 seconds prior to to stopping the old capture.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@xxxxxxx
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Amit Vashisht [mailto:amitv@xxxxxxxxxxxxxx] 
> Sent: Friday, February 21, 2003 3:23 AM
> To: ethereal-dev@xxxxxxxxxxxx
> Subject: [Ethereal-dev] Need Urgent Help - Maintenance of 
> Tethereal state information
> 
> 
> Hi,
> 
> It appears that tethereal/ethereal maintains state 
> information ( in some
> specific circumstances ) as per an earlier message of the mailing list
> (http://www.ethereal.com/lists/ethereal-users/200211/msg00022.html).
> 
> I quote Ronnie Sahlberg
> ">>>>> .... The state in question is the stuff ethereal 
> remembers internally
> about every packet it sees, information such as when the 
> packet was received,
> size of it,
> 
> >>>>> .... every packet will still add to the state buildup 
> inside ethereal
> 
> until you reach a point where memory is exhausted.I.e. 
> ethereal will become
> slower and slower as memory is exhausted on the system.
> 
> >>>>>>.... Stoping and restarting the capture is an efficient 
> method to
> 
> control the amount of state buildup. "
> 
> In our usage scenario , the packets need to be captured for 
> long durations of
> time at a stretch ( maybe months , may even be years ) and 
> therefore memory
> exhaustion may not be acceptable ,
> 1. Is it possible to CLEANUP the STATE INFORMATION when 
> switching between
> capture files in the ringbuffer ?
> 2. If yes , Which function calls can be made to cleanup such state
> information ?
> 3. Stopping and restarting capture as suggested above would 
> not be viable as
> that may involve the undesirable missing of a few packets . 
> Is there any
> other possible technique to cleanup the state information ?
> 
> Thanks ,
> Amit Vashisht
> 
> *********************************************************
> Disclaimer
> 
> This message (including any attachments) contains 
> confidential information intended for a specific 
> individual and purpose, and is protected by law. 
> If you are not the intended recipient, you should 
> delete this message and are hereby notified that 
> any disclosure, copying, or distribution of this
> message, or the taking of any action based on it, 
> is strictly prohibited.
> 
> *********************************************************
> Visit us at http://www.mahindrabt.com
> 
> 
> 
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>