Nope... that's ntop's behavior. Externally to ntop, you could try pinging all the hosts on your network to cause their data to be reloaded... don't know for sure it would work, but it's logical.
read the FAQ entry about -S at http://snapshot.ntop.org -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jorge Daza Garc�a-Blanes Sent: Tuesday, May 07, 2002 7:39 AM To: Ntop ML Subject: [Ntop] Problems with old entries Hello, I'm using ntop with "-S 2". It stores information only when dying. That's not so bad because I have a cron job that kills it periodically. My problem is with that "http://host/dumpData.html?language=Perl"; Let's say that you have information from hosts A and B. You use dumpData and dumps the information for both. Then you kill ntop, and restart it again. Then there is no activity from host B, but there is for host A. You use dumpData again and you only get information for host B. You do not get information from old hosts that are still in the db, but that have not been active since last restart. Is there any way to override that behaviour ? Thanks in advance, Jorge -- Jorge Daza Garc�a-Blanes Software Development / Technical Director triple-e / european electronic effects GmbH Vestische Strasse 46 46117 Oberhausen Germany Fon: +49 (0) 208 8990 418 Fax: +49 (0) 208 8990 119 e-mail: [EMAIL PROTECTED] web: www.triple-e-vfx.com _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
