If you have the free memory, increase it. And yes, you can tweak the timers, but I think you'll need to recompile.
I currently have address resolution and sessions disabled due to frequent segfaults. Are you running the latest from SVN? What's its version info? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of James Chase Sent: Wednesday, September 16, 2009 1:24 PM To: [email protected] Subject: [Ntop] Maximum Number of TCP Sessions Reached (32768) I've been getting this a lot lately. We are using the default of (32768). We do see a lot of hosts but is there a good resolution for this, or should I just ignore it? Can you set ntop to purge idle hosts more frequently, or is it safe to add more RAM and change the maximum number of TCP sessions allowed? Is the stability of ntop affected at all when maintaining information about too many hosts? By the way -- the dev version of ntop does not appear to have webserver crashes in CentOS/RHEL environments like the current stable version does. FWIW Thanks _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font> _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
