From owner-freebsd-questions Sat Nov 11 14:53: 4 2000 Delivered-To: freebsd-questions@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 56E3037B479 for ; Sat, 11 Nov 2000 14:53:01 -0800 (PST) Received: from petri2000 ([194.192.131.97]) by distortion.dk (8.9.3/8.9.1) with SMTP id XAA91811 for ; Sat, 11 Nov 2000 23:58:48 +0100 (CET) (envelope-from nicolai@petri.cc) Message-ID: <006b01c04c32$25a24080$6732a8c0@atomic.dk> From: "Nicolai Petri" To: Subject: ntop current [multithreaded] crashes hard on FreeBSD.. Date: Sat, 11 Nov 2000 23:53:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone explain what is wrong with the use of threads on FreeBSD that ntop uses ? I've looked real hard into it, but I can't find a solution.. Anyone up for the challenge ?? Btw. It's really a great network monitor.. So use it or ... don't ... You'll need to check out the latest thru cvs for autoconf to detect threads on FreeBSD. ----------- CVSROOT=:pserver:anonymous@cvs.ntop.org:/home/ntop export CVSROOT cvs login cvs checkout . Password is ntop ----------- To make it crash simply hold down the reload button in your browser.. It's a sure thing.. It also have a problem with some graphs.. But that seems to disappear when using a newer version of gd and gdchart.. Please help.... And I'll give a beer.. (In Denmark :o) --- Nicolai Petri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message