On Tue, 2007-09-18 at 21:23 +0200, Michael Meskes wrote: > On Tue, Sep 18, 2007 at 09:13:13AM -0700, Ross Boylan wrote: > > > Could you please apply the small patch attached to the statnet client > > > and try again? I applied the patch and observed the following behavior consistently: 1. Login to KDE, start a Konsole, run statnet, do a litle web activity, logout. Works fine. I'm not sure if the good behavior is new with the patch, or if I'm just noticing the pattern. I thought statnet needed to run as root. 2. Login to KDE, start Konsole, sux, run statnet, do a little web activity (as regular user), logout. 100% CPU when I log out.
Do you want me to collect and strace or debug? In the latter case, how do I build the package for debugging? > If this does not solve it I might need you to run a > > > little bit of debugging for me. Do you understand C code? > > Yes. > > Does this mean the patch doesn't help? > > If so, my next ideas would be to remove the signal handler stuff and go > with the drfault signal handler. If this doesn't help I'd like to have > some outpout added preferable to a file to see where the program is > while running amok. > > > It's odd the problem isn't more repeatable. I'm running statnet inside > > a KDE Konsole, if that matters. > > Hmm, I ran it in an xterm under KDE to no avail, maybe I should try > konsole too. > > Michael > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
