>OK, but WHICH version of ntop? Sorry about that, the version is 3.0 >The trap code worked, but what was it trapping???? I have no clue. All I could find about the problem was the entries in the submitted log. If there are places I haven't looked at, please let me know.
>...although it would be nice to have the stats from the problem report to see >how many hosts ntop 'knows' about. Unfortunately, the data was lost with the ntop crash. However the total amount of hosts were close to 200 pages, and since ntop shows 130 hosts per page, that would be approximately 26000 hosts collected through NetFlow. Please note however that this is my approximation, not a fact! >For practical purposes, you should probably configure your logrotate with a >size limit too. Or even move to a more robust log. I use metalog on my >Gentoo systems - it manages the log file size on each message, rather than a >cron-driven logrotate. That would have prevented your log filling up the >system. That's very true, however this instance of ntop was installed on a system which already had Redhat ES 2 installed, and I'm not allowed to use any other distribution than RH fedora or ES (Unfortunate company policy). I'm well aquainted with the benefits of metalog (I'm running it as well on a few private machines) but trying to mess with redhat is often a bad idea, and this system in particular is rather a mess. I'll have a few things changed when I get the hardware for "my" system. //Niklas Berggren. _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
