On Sun, 2007-09-30 at 14:13 +0200, Michael Meskes wrote: > On Sat, Sep 29, 2007 at 09:58:10AM -0700, Ross Boylan wrote: > > 2. Login to KDE, start Konsole, sux, run statnet, do a little web > > activity (as regular user), logout. > > 100% CPU when I log out. > > Now I understand. This is not a statnet bug. Please try the same setup > with "ls -R /" for instance and you'll notice the same behaviour. It's a > result of how konsole is terminated. If you kill it with a signal, statnet > should also disappear. Why does this depend on the user I'm running as? > > It seems that the ncurses functions do not notice that their display > disappeared and, even worse, the timeout() function returns immediately > which results in statnet grabbing the CPU all the time. > > However, I don't think this is really a statnet bug. Should this be reassigned to ncurses? konsole?
Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
