I am running ntop 2.0 beta on Redhat 7.1. If I leave it running for around a
week with ntop -S 1 to save host stats. The hostsInfo.db file can grow to >
2Gb in size. This is with gdbm as the db backend. Any idea for some kind of
purging without looseing all the data ?
One other thing I notice when I dump the keys for hostsInfo.db. There are
duplicate keys within.
Francis Pintos
week with ntop -S 1 to save host stats. The hostsInfo.db file can grow to >
2Gb in size. This is with gdbm as the db backend. Any idea for some kind of
purging without looseing all the data ?
One other thing I notice when I dump the keys for hostsInfo.db. There are
duplicate keys within.
Francis Pintos