The single threaded mode is basically unsupported. There's just too much going on in ntop for it to be safe.
It does seem kinda odd, however, I'll grant you that. First thought is to just rip it out... -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sumit Pandya Sent: Monday, March 24, 2003 11:37 PM To: [EMAIL PROTECTED] Subject: Re: [Ntop-dev] ntop multri threading issue ----- Original Message ----- From: "Burton M. Strauss III" <[EMAIL PROTECTED]> > > 2) gcc 2.91 is very old. I've frankly never used anything that old with > ntop (2.96 is shipped w/ RedHat and most distros now ship 3.0.4 or 3.2). > I'm guessing that there's a problem with the support for the POSIX threading > stuff. It would be nice if someone point out kind of problem with POSIX threading in egcs-2.91.66 19990314 ? Okay threading can be problem but again without threading code is, if we look into code there is a alarm call on line 236 of ntop.c ------ snip ------------- void detachFromTerminal(int doChdir) { #ifndef CFG_MULTITHREADED alarm(120); /* Don't freeze */ #endif ------ snip ------------- And SIG_ALRM is not been cought anywhere in the code. Thus if ntop runs in the daemon mode then due to that signal this daemon is killed after 120 sec. This process run and serve the intended purpose if it is not daemonized i.e running without "-d" option. Any hints for SIG_ALRM signal handler? Moreover in http.c SIG_ALRM causes this process to call quitNow and exits the process, Strange for me at least Burton? Thankx, -- Sumit > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of atit jariwala > Sent: Monday, March 24, 2003 1:22 AM > To: [EMAIL PROTECTED] > Subject: [Ntop-dev] ntop multri threading issue > > > Hello, > I am using RedHat Linux Kernel 2.2.14-12. > gcc version: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) > and > autoconf-2.53 automake-1.6.3 libtool-1.4.2 . > > I found following problems with ntop > > with ntop 1.2.57 , 2.1.58 and 1.2.59 > > if i configure with multi threading enabled then i got following message: > "Started thread <thread-id> for network packet analyser" . > above is message from function initThreads() in initialize.c > then it will block... So it is not creating http socket ( which must at port > 3001 in my case) > so It will block after creating one thread........... > > if i configure with multi threading disabled, then i will run ntop in deamon > mode , it will start ntop > successfully,create socket at port 3001. > and in ntop.c will set alarm(120) > but it is not catching SIGALRM signal.. > > and in http.c it will set alarm(120) and catch SIGALRM and then call > quitNow() function.... _______________________________________________ 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
