Hi, I am using the latest CVS ntop, on a Suse 9.1 box, 2x3.0Ghz Xeon + 1.5GB RAM, and it will run for varying amounts of time (so far the record is ~ 9 hours) before crashing.
------------------------------------------------------------------- Oct 28 00:25:59 linux ntop[3161]: NETFLOW: createNetFlowDevice created device 1 Oct 28 00:25:59 linux ntop[3161]: Now running as requested user 'ntop' (1000:100) Oct 28 00:25:59 linux ntop[3161]: INIT: Created pid file (/usr/local/share/ntop/ntop.pid) Oct 28 00:25:59 linux ntop[3161]: Note: Reporting device initally set to 1 [EHR] Oct 28 00:25:59 linux ntop[3161]: THREADMGMT: pcap (eth0) dispatch thread running... Oct 28 00:25:59 linux ntop[3161]: THREADMGMT: Started thread (1114135472) for network packet sniffing on eth0 Oct 28 09:58:02 linux out of memory [3161 r^E^Hout ] -------------------------------------------------------------------- ntop Configuration ntop version.....3.0.053 Configured on.....Oct 27 2004 2:33:08 Built on.....Oct 27 2004 02:33:32 OS.....i686-pc-linux-gnu libpcap version.....libpcap version 0.8 ntop Process Id.....7563 http Process Id.....7563 It is lasting this much because I enabled --track-local-hosts and disabled DNS, otherwise it would be crashing within several minutes. I am receiving 5 NetFlows, and as of now there are 271 active end nodes. CPU utilization never goes above 3%, and with --track-local-hosts, the highest memory utilization was around 50% before it died. What can I do to stop it from going down, and possibly even disable --track-local-hosts so I can see where connections are ending ? Thanks, Stefan. _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
