|
Well, they do different things...
Your change affects the time before ntop may choose to
purge. This affects both HOSTS and SESSIONS.
A host w/ no active sessions and no traffic is considered
idle and can be selected for purge. This purges the whole kit and
kaboodle.
Individual sessions may also be purged on the same
schedule.
But you had also found that the command line switch wasn't
being honored.
ntop used to - by mistake - treat a closed session as
instantly eligible for purge. So you never saw data for recently ended
sessions in that part of the web server. But when I fixed
the bug, I was concerned that this could - under some situations - cause a huge
increase in the number of sessions being tracked and thus memory usage. So
I defaulted to the old behavior and added the switch to make ntop work
correctly. I've just never gotten around to flipping them the way they
should be.
-----Burton
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 22, 2006 4:10 PM To: [email protected] Subject: RE: [Ntop] Newbie questions Didn’t realize you added a patch for me! I had already got into global_defines.h and reversed the setting J
Nathan Choate Sr. Network Administrator J-W Operating Company Longview, TX (903) 291-2820 direct line (903) 235-4417 cell
-----Original
Message-----
You probably want to make sure you are using the CVS version - or pick up the patch I added recently for Nathan - otherwise, ntop ignores the --disable-instantsessionpurge option.
-----Burton
(Search the back traffic on ntop-dev for my ref 704 - that will give you the file(s) to diff).
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED] If you don’t want to use the sticky hosts option but want to retain info a little longer and If you are up to the task, you can edit the global_defines.h which sets a number of values at compile time.
In my case I changed some of the idle timeout settings that control the purge behavior with some good results. Look for the PARM_HOST_PURCH_MINIMUM_IDLE params and others in there to keep the recorded sessions a little longer. I played with those and got them to keep the last couple of days. As someone mentioned just before, the sticky hosts can fill up your tables if you leave it running for long periods. There are plenty in there to keep you busy tweaking.
Nathan Choate Sr. Network Administrator J-W Operating Company Longview, TX (903) 291-2820 direct line (903) 235-4417 cell
-----Original
Message-----
Hello there, |
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
