Sounds great, (was running yesterday's CVS, 1/31/03). Regards
On Fri, 2003-01-31 at 18:58, Burton M. Strauss III wrote: > Of course, none of you are indicating what version(s) of ntop you're > using... if it's not .55 (SourceForge) or .56pre (cvs), then update your > versions. > > A basic host record (no sessions) is only 8 or 10KB. A server can eat a lot > more, but still... > > I have a couple of patches almost ready to go in which will > > 1. Add some memory tracking info to the logs. DONE > > 2. Convert myGlobals.capturePackets from 0/1 to a tri-state (run, stopcap, > term) > In stopcap: > The last rrd data should be saved > The web interface is still up (static) so you can see the memory > tracking data > You can cleanly shutdown. > > 3. Add logic to ntop_safemalloc (et al) to trap a malloc() error, report is > and change the state from run->stopcap > > > > What will be of interest is these sections from textinfo.html: > Memory allocation - data segment > Memory allocation - mmapped > Host Memory Cache > Host Hash counts > > > -----Burton > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Arnt > Karlsen > Sent: Friday, January 31, 2003 2:16 PM > To: [EMAIL PROTECTED] > Subject: Re: [Ntop] RE: Ntop crashing and memory usage > > > On Fri, 31 Jan 2003 12:04:37 -0500, > "Ashley Gates" <[EMAIL PROTECTED]> wrote in message > <[EMAIL PROTECTED]>: > > > I have mentioned a similar problem before. > > > > I have a PII-450 with 1 gigabyte of memory and it still crashes! > > > > I use a 7204 VXR with a /20 and using IP flow-export to receive the > > stats. > > > > I would agree that enough memory is necessary but ntop will eat 900 > > megs of RAM in a little over an hour!! > > ..something is dead wrong here: I set up ntop-2.1.3 on a Red Hat-7.3 > based bandwidth trottle, hung outside my isp's (and client's) gateway, > serving a "/23" net (actually a 2 /25, 2 /26, a /27 and an untrottled > /27 link net), on an athlon 1.2GHz w 128MB ram. Ran for weeks, until > the box was upgraded to RH's 2.4.18-18 kernel, which didn't like ntop > and/or vice versa. In my own house (surf traffic only) lan, I tried > it on a 450MHz K6-2 with both 128 and 384 MB, and it died (out of > lonelyness?) in an average 5 minutes. > > ..Luca, Burton, what do you guys need us to test? > > -- > ..med vennlig hilsen = with Kind Regards from Arnt... ;-) > ...with a number of polar bear hunters in his ancestry... > Scenarios always come in sets of three: > best case, worst case, and just in case. > > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop > > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop -- Michael Baird <[EMAIL PROTECTED]> _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
