Date: Wed, 3 Nov 1999 19:10:01 +0100 (CET) From: Marc Schneiders <marc@oldserver.demon.nl> To: Antti Kantee <pooka@iki.fi> Cc: freebsd-questions@freebsd.org Subject: Re: trouble with ntop & 3.3-RELEASE Message-ID: <Pine.BSF.4.10.9911031906580.4465-100000@propro.oldserver.demon.nl> In-Reply-To: <19991103154908.B10021@cs.hut.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Nov 1999, Antti Kantee wrote: > 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 > My reply does not help, but provides maybe some consolation. When I run ntop (from the ports) on 4.0 current, it tries to eat up an awful lot of CPU time. Over 50% on a dual PPro 200 MHz. I haven't been able to find a solution/explanation and now run ntop on a different machine/OS. Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 7:06pm up 7 days, 12:47, load average: 2.11 2.06 2.01 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9911031906580.4465-100000>