From owner-freebsd-questions Wed Nov 3 5:49:47 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cyberneti.cs.hut.fi (cyberneti.cs.hut.fi [130.233.193.247]) by hub.freebsd.org (Postfix) with ESMTP id DBB221544F for ; Wed, 3 Nov 1999 05:49:39 -0800 (PST) (envelope-from pooka@cyberneti.cs.hut.fi) Received: (from pooka@localhost) by cyberneti.cs.hut.fi (8.9.3/8.9.3) id PAA10621 for freebsd-questions@freebsd.org; Wed, 3 Nov 1999 15:49:08 +0200 (EET) Date: Wed, 3 Nov 1999 15:49:08 +0200 From: Antti Kantee To: freebsd-questions@freebsd.org Subject: trouble with ntop & 3.3-RELEASE Message-ID: <19991103154908.B10021@cs.hut.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a box I remote administer but ever since I upgraded from a snapshot between 3.0 and 3.1 to 3.3-RELEASE I've had problems. Running ntop can freeze the entire box (or does something to make it unaccessable from outside. I don't know what because I've never been there to boot it after the crash). With the snapshot release there never were any problems, and the box was up 170days in a row. Well that could be partly due to the fact that it was running a GENERIC kernel and no bpf and therefore no ntop was available ;) Some facts about the hardware I'm gathering from my head (since the box is down at the very moment) processor: ppro mem: 96megs Network interface: 3com 3c905 (or atleast something that uses xl-driver) Does someone have constructive suggestions apart from pkg_delete ntop? TIA ps. please cc me as I'm not on the list -- "Never underestimate the power of the Lite side of the \Source/" Antti Kantee / NetBSD \ 1973 <- draken \ / o / http://www.netbsd.org \ platters -> 1999 \ / | ______________/ Free Multiplatform UN*X \___________________\/__ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message