Lots - did you read docs/FAQ and the back traffic on this list on this very topic?
No you didn't... bad user - no candy and cookies for you! Q. I remember rumors about something not being right under FreeBSD with threads? A. Yes. See FreeBSD bug bin/17437 at http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17437 Basically, due to limits in FreeBSD, there is no pthread_atfork() function. So, when ntop does it's fork() call to create http pages, it can't fixup the Mutexes. It wrong and could conceivably cause problems. However - ntop ran for years without the pthread_atfork() code, so we're no worse off in 3.0 under FreeBSD than in 2.2 or 2.1... There was a flurry of problems late in the 3.0 development cycle having to do with a seeming deadlock of the ntop web server (it's actually not dead, just walking at about 0.001KPH). Thanks to Yeoman efforts by Stanley Hopcroft, Michal Meloun and, well, me, we have a work-around. If you're running under FreeBSD, use the flag, --set-pcap-nonblocking. For more on this, read the threads at gmane - look for "FreeBSD and pthreads" - that's probably the best summary. But there's stuff on this back at least to October 2003 - look for Stanley's problems with CPU usage. -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Eirik Oeverby > Sent: Friday, July 02, 2004 8:05 AM > To: [EMAIL PROTECTED] > Subject: [Ntop-dev] High CPU load on FreeBSD with -p option > > > Hi all, > > For some time now I have struggled with ntop on some (not all) of our > FreeBSD machines. In particular, a FreeBSD 5.2.1 machine is giving me > headaches: > > When running ntop (3.0) with the -p <protocol list file> parameter, > after a short while its CPU load skyrockets and stays at 100% (actually, > 100% of one of the CPUs in the server). Removing the -p parameter > normalizes the situation. > Note that while the CPU load is high, ntop seems to be behaving as it > should, i.e. it collects traffic data and respons to webserver requests. > There's no obvious slowdown, though this is a dual opteron server so I > don't usually notice slowdowns anyway. > > Also note that the --set-pcap-nonblocking option makes no difference; it > probably has no significant effect on FreeBSD 5.x. > > On another server (FreeBSD 4.10), I have no problems with the -p > parameter whatsoever. > > Anyone got any clue what's up with this? > > Best regards, > Eirik �verby > Unicore AS > Oslo, Norway > > > _______________________________________________ > Ntop-dev mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
