For some reason I cant get ntop to run properly for more then 2 hours. I'll admit we have a huge pipe to monitor but this time its a bit different.
The kernel reports that ntop has exited on signal 11, the ntop logs show something pecualiar as well - ex: graback ntop[pid]: totIpBytesSent=3032459259, totBytesRcvd=3 various lines of that for a good 40-45 minutes before the last sig 11. Anyone have any clues to this? I was having trouble running in non-border mode since there just way to much traffic for it to proccess. So i used the -j option in the command line and added the subnets manualy and the machine load went down by far and it seemed to be performing a lot better. However, it crashed again after a couple of hours with those messages. Any ideas/comments are greatly appreciated. -- Tony Hernandez Computer Programmer Analyst Division of Housing University of Florida "All your base are belong to us!" - Zero Wing _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
