Package: ntop Version: 2:3.0-5 Severity: normal Whenever we run ntop for a while (a day or two, sometimes shorter) on a fairly standard Debian sarge system, one of the ntop processes gets out of hand and takes all available CPU cycles, and thus needs to be killed.
The only thing that might be a bit different about this system is the custom kernel, currently 2.6.16.2. If a kernel issue could be implicated, I can provide the kernel config, but it seems to me unlikely. Any ideas about how to better isolate the problem and prevent it from happening? -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.16.2-bluesky Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages ntop depends on: ii debconf 1.4.30.13 Debian configuration management sy ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgd2-xpm 2.0.33-1.1 GD Graphics Library version 2 ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime ii libjpeg62 6b-10 The Independent JPEG Group's JPEG ii libpcap0.7 0.7.2-7 System interface for user-level pa ii libpng12-0 1.2.8rel-1 PNG library - runtime hi libssl0.9.7 0.9.7e-3sarge1 SSL shared libraries ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- debconf information: ntop/createuser: false * ntop/interfaces: eth0 * ntop/trace: 0 * ntop/port: 3000 * ntop/save: 0 * ntop/user: ntop ntop/usernotice: * ntop/getopt: * ntop/mode: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
