WRT to memory usage, look at docs/FAQ. But basic answer is LOTS. ntop creates a HostTraffic structure for every host it sees - this runs 4-12K+. The hosts you see are controlled by external forces, not ntop. You can use various switches, e.g. --track-local, and filters to control what is stored, but it's dependent upon users... If you have somebody running port scans against a /8, well, you could get hit with 16M of hosts...
-----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ola Lundqvist Sent: Tuesday, April 26, 2005 12:10 AM To: [email protected]; Burton Strauss Cc: [EMAIL PROTECTED] Subject: Re: [Ntop-dev] Debian bugs. <snip /> > > #288006: ntop leaks memory > Package: ntop; Reported by: Jerome Warnier <[EMAIL PROTECTED]>; > 114 days old. > > Response: See (2) How much memory can you expect ntop to use on a high traffic network? It is good for me to know what is a valid range. It will be retested on 3.1 as far as I get it working. Thanks for your time. Regards, // Ola <snip /> _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
