From owner-freebsd-net@FreeBSD.ORG Sat May 7 15:45:16 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92E1916A4DB for ; Sat, 7 May 2005 15:45:16 +0000 (GMT) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 15EC643DA5 for ; Sat, 7 May 2005 15:45:16 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from unknown (HELO 172.16.0.1) (mikej@69.193.222.195 with login) by smtp103.rog.mail.re2.yahoo.com with SMTP; 7 May 2005 15:45:15 -0000 Received: from 172.16.0.199 (SquirrelMail authenticated user mikej) by 172.16.0.1 with HTTP; Sat, 7 May 2005 11:45:21 -0400 (EDT) Message-ID: <1489.172.16.0.199.1115480721.squirrel@172.16.0.1> In-Reply-To: <70e8236f05050708204937ded0@mail.gmail.com> References: <70e8236f05050708204937ded0@mail.gmail.com> Date: Sat, 7 May 2005 11:45:21 -0400 (EDT) From: "Mike Jakubik" To: "Joao Barros" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-net@freebsd.org Subject: Re: ntop on FreeBSD 5.4ish and threading X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 May 2005 15:45:16 -0000 On Sat, May 7, 2005 11:20 am, Joao Barros said: > Hi all, > > > I recently tried ntop on FreeBSD 5.4 RC3 and RC4 and was disappointed > with the problems I bumped into. I reported this to ntop's developers > mailing list and a few coments about FreeBSD threading came up. It would > be interesting if someone could take a look at the thread I started: > http://listgateway.unipi.it/pipermail/ntop/2005-May/010397.html > > > My thanks in advance, Ntop is badly broken on FreeBSD, has been for a while. I reported this a long time ago to the port maintainers, but nothing. It should be removed from the ports tree.