Inactive hosts are purged - on a probalistic basis (given enough time, all inactive hosts will be purged, but for any particular purge cycle a particular host might not be).
Active hosts are NOT purged. -g basically directs all non-local hosts to the 'other host' entry - the stats get recorded but not the details. IIRC, using sFlow/netFlow, -g does NOT have an effect - the non-local host info IS still recorded. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Garvin Hicking Sent: Friday, March 07, 2003 11:46 AM To: [EMAIL PROTECTED] Subject: Re: [Ntop-dev] Memory usage and dying (ntop 2.1.55) Hi Burton! > Unique hosts are what causes ntop to use memory. But I thought the hosts are purged somewhere? For my situation it seems as if a list constantly grows. How can I restrict logging of the hosts? Does the '-g' option ('track only local hosts') mean that no external traffic is logged, or does it only mean that I get no host-related information of traffic to those hosts? I just want to use ntop for logging transferred bytes on specific ports, and total sums of them...I have no use for any hostnames to which I connect to, or at least I only need that information temporarily and not traced over X hours. I hope I'm not being unspecific? :) Thanks for your time, Garvin. _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
