Package: netdiag Version: 0.7-7 Severity: normal I have repeatedly observed that if I logout and then log back in statnet consumes most of the CPU until I kill it. For example, I currently see $ ps -lC statnet F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD 0 R 1000 25972 1 0 74 0 - 473 - ? 00:08:58 statnet 0 S 1000 3840 3723 0 69 0 - 473 poll pts/10 00:00:00 statnet
25972 is the one taking the CPU. I suspect it is leftover from the first session, so there may be something wrong with the kill logic. Details: I run KDE and my standard session includes a terminal running statnet. When I logoff that terminal is one of the things still on the screen. In this case I restarted the X server; I'm not sure if that's necessary for this problem. When I log back in the terminal with statnet is restored and works properly. However, the other statnet eats my CPU. SIGTERM kills it and solves the problem. I'm not sure how long this has been going on, but my sense is that awhile ago this was not a problem. I could be wrong about that. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27advncdfs Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages netdiag depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libncurses5 5.4-4 Shared libraries for terminal hand ii netbase 4.20 Basic TCP/IP networking system -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
