Once it hits maximum, it will not store additional sessions:
if(myGlobals.device[actualDeviceId].numTcpSessions >=
myGlobals.runningPref.maxNumSessions) {
static char messageShown = 0;
if(!messageShown) {
messageShown = 1;
traceEvent(CONST_TRACE_INFO, "WARNING: Max num TCP sessions (%u)
reached (see -X)",
myGlobals.runningPref.maxNumSessions);
}
return(NULL);
}
You'll need to trace what would cause numTcpSessions NOT to eventually be
decremented.
However, -X and -x are crude, chain-saw types of limits and side-effects
aren't surprising.
You should probably move this discussion to ntop-dev as you start tracing
the code.
-----Burton
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Marius Onica
Sent: Thursday, July 28, 2005 4:16 AM
To: [email protected]
Subject: [Ntop] cvs problems - max num tcp session
Hi,
It seems that the cvs ntop has a problem when started with the -X
(max.num.tcp session). Namely, after reaching the max number tscp sessions
ntop stops measuring any throughput. For example in the network load it
shows zerro throughput, in the host information table it shows that every
host is inactive.
Any ideas ?
TIA,
Marius
______________________________________
Inflex - installed on mailserver for domain @uoradea.ro Queries to:
[EMAIL PROTECTED] _______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
