Luca, FYI - After about 24 hours NTOP 5.0 is still running using the -c option.
On 07/23/2012 10:57 AM, Steve Clark wrote:
Hi Luca, If I had to guess I think it is in the sticky host/purge idle host. I was seeing the problem within 15 minutes of starting NTOP until I turned on sticky-hosts -c. NTOP has now been running for over 3 hours with [473 active ] [1148 total ] hosts. Notice purgeIdleHosts() is in the call path. /lib/libc.so.6[0x42dfe1] /usr/local/lib/libntop-5.0.so(ntop_safefree+0x2d)[0x1caf7d] /usr/local/lib/libntop-5.0.so(deleteFragment+0x51)[0x1be391] /usr/local/lib/libntop-5.0.so(purgeOldFragmentEntries+0x9c)[0x1be6cc] /usr/local/lib/libntop-5.0.so(purgeIdleHosts+0xd3)[0x1bc753] /usr/local/lib/libntop-5.0.so(scanIdleLoop+0x230)[0x1cbaa0] On 07/23/2012 03:48 AM, Luca Deri wrote:
-- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: [email protected] http://www.netwolves.com
_______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
