Definitely. 2.1.3 is A LOT better than 2.0.99 whatever. But there's a lot of progress since then, both stability and features. With 2.2 coming soon (I hope), nobody has any development interest in 2.1.3 either.
It's not the formality, it's the total lack of information - the expectation that I can read people's minds, CPUs and screens at a distance. Hopefully, the new built-in 'problem report' will eliminate a lot of that. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tony Hernandez Sent: Friday, February 21, 2003 10:45 AM To: [EMAIL PROTECTED] Subject: RE: [Ntop] Ntop crashes after ~2hours in border mode I will do that, thanks for the info. I was acutally just made aware by a colleuge that we where not running the latest version. So we are building it now. I know my requests have been a bit informal, and I'm sorry for that . I guess just a bit of laziness on my part =) It was actually 2.0.99 R2 - which consequentially was in the freeBSD ports and hasnt been updated since july of last year ?!?! Hopefully it will be a bit more stable. funny thing is it wouldnt even run for 2 minutes anymore.. it seemed to get progresively worse till it would not run anymore. Hopefully we'll be in the clear - or clearer somewhat with the latest stable. You think I should run the dev versions other then the latest stable(2.1.3)? Again sorry for the informality - -----Original Message----- From: Burton M. Strauss III [mailto:[EMAIL PROTECTED]] Sent: Friday, February 21, 2003 11:22 AM To: [EMAIL PROTECTED] Subject: RE: [Ntop] Ntop crashes after ~2hours in border mode How about the usually requested information - ntop version et al... See How To ask for help in the docs/FAQ or at http://snapshot.ntop.org Never-the-less, since you say -j, I'm guessing it's 2.1.3. The current development version is 2.1.57 or 2.1.58pre and that's what we're focused on. In those versions, -j has been replaced by 4 more granular switches. Plus lots of bug fixes, etc. Give the latest version a try. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tony Hernandez Sent: Friday, February 21, 2003 9:29 AM To: [EMAIL PROTECTED] Subject: [Ntop] Ntop crashes after ~2hours in border mode 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 _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
