-X's units are # of entries. If you look on the info.html report (About | Configuration), there's a 'very approx' memory per host measurement.
That should give you a starting point. Two notes: (1) -X (and -x) are unsophisticated chainsaw type approaches - they just STOP allocating at the limit, regardless of whether they should. (2) You are far better off looking at the other switches and using filters to make ntop monitor the RIGHT things. -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Egger > Lothar > Sent: Saturday, April 03, 2004 8:11 AM > To: '[EMAIL PROTECTED]' > Subject: [Ntop] -X option > > > hi all > > can i stop ntop from eating up all available memory on my box? > up to ~500MB. > > is the -x option the right way todo so? > and what do i have to type in ? (max of hash/list entrys? b, kb, MB) > > any help would be appreciated. > > thank you for your work > > regards > lothar egger > > ###### > -x > > -X > ntop creates a new hash/list entry for each new host/TCP > session seen. In case of DOS (Denial Of Service) an > attacker can easily exhaust all the host available memory > because ntop is creating entries for dummy hosts. In > order to avoid this you can set an upper limit in order > to limit the memory ntop can use. > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
