Short answer: No Longer answer:
ntop's base memory needs are pretty small... call it 7-8 MB (this covers the program and a small home lan - 3-4 hosts contacting a few web sites). However, ntop stores information about all of the hosts that it sees which are active. This is a non-trivial amount of memory per host (I actually don't remember what it is). What this means is that if you are positioned on a busy segment (say a corporate backbone), you will use a large amount of memory. Memory is cheap - if this is a corporate situation, then my answer is to spend a $100 and add a GB of ram. If that's not an option, you need to 1. Place your ntop sensor carefully 2. Use the -B "bpf filter" command to limit what you are reporting on in both cases to see what is important to you and will fit within memory. For example, say you don't care about the 1M web sites your users are viewing... ntop ... -B "not port 80" If you are running ntop on your ingress router but don't care about the rest of the network, just your part - the use -i to select only the one interface... etc. -----Burton ---------- Original Message ---------------------------------- From: Inaki Sanchez <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Tue, 02 Jul 2002 13:07:14 +0200 > Hi all: > > Is there a way, for ntop 2.0.99rc2 to limit the amount of memory to >use? In previous versions there was "-s hash-size", which has >disappeared. I've got a box with 256 Mb. of RAM, and ntop is using >+370Mb, with a hostsInfo.db file of 450 Mb. > > Thanks, > > --Inaki. >_______________________________________________ >Ntop mailing list >[EMAIL PROTECTED] >http://lists.ntop.org/mailman/listinfo/ntop > __________________________________________________ D O T E A S Y - "Join the web hosting revolution!" http://www.doteasy.com _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://lists.ntop.org/mailman/listinfo/ntop
