Well the alarm() call is set in the fork()ed child that handles http generation for the 'read only' pages (look through http.c for the code). Means that ntop spent 15s trying to generate the page and never finished.
Either it's deadlocked or you just have too much data? But I'd vote for deadlock... ----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Tamas MEZEI > Sent: Wednesday, April 21, 2004 7:54 PM > To: [EMAIL PROTECTED] > Subject: [Ntop-dev] ntop3, openbsd-current lock > > > Hi, > > I'm using Julien's latest openbsd port, standard libpcap and stuff. > Ntop3 starts working nicely, and after about an hour it just simply > says: > **ERROR** http generation failed, alarm() tripped. Please report this to > ntop-dev > > And the machine hangs. > > Any ideas what has happened? :/ > > Thanks, > > Tamas > _______________________________________________ > 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
