I fired up the 3.0 version to find that the disable-instantsession purge was NO by default.
Now you're saying that in 3.2 it's set to YES by default with now way to turn it off? I have looked at the globals-defines.h file you mentioned. Is there any settings I can make there, to set the behaviour back to where it won't run out of max sessions? My network isn't so busy that were running that many session over a 5m span. It definitely grows over a time of several hours until it max's out. Nathan Choate -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burton Strauss Sent: Thursday, March 30, 2006 6:08 PM To: [email protected] Subject: RE: [Ntop] NTOP fails because of max sessions reached --disable-instantsessionpurge should be the default ... It is the correct functionality. We simply didn't want to make a big change like that just before the release. I need to check the ./configure stuff and correct the docs - maybe make the option --enable-instantsessionpurge or some such. -----Burton _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
