From owner-freebsd-questions@FreeBSD.ORG Tue Jul 15 12:27:37 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A40DB37B401 for ; Tue, 15 Jul 2003 12:27:37 -0700 (PDT) Received: from anyfloridahome.com (adsl-068-153-193-052.sip.bct.bellsouth.net [68.153.193.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADC3B43F93 for ; Tue, 15 Jul 2003 12:27:36 -0700 (PDT) (envelope-from bob@anything-inc.com) Received: from neo.anything-inc.com [68.153.193.50] by anyfloridahome.com with ESMTP (SMTPD32-6.00) id A6EB6D0066; Tue, 15 Jul 2003 15:32:59 -0400 Message-Id: <5.2.0.9.0.20030715152419.00af08e8@mail.anything-inc.com> X-Sender: bob@anything-inc.com@mail.anything-inc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 15 Jul 2003 15:25:01 -0400 To: freebsd-questions From: Bob Collins In-Reply-To: <200307151420.44792.racerx@makeworld.com> References: <20030715191421.GQ60879@freshaire.wiz.com> <000301c34b03$22d18f50$010b0a0a@windstorm> <12344.1058296284@www21.gmx.net> <20030715191421.GQ60879@freshaire.wiz.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: KDE process is unkillable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 19:27:38 -0000 At 03:20 PM 7/15/2003, you wrote: >On Tuesday 15 July 2003 02:14 pm, Marc Wiz wrote: > > On Tue, Jul 15, 2003 at 09:11:24PM +0200, daniela5743@gmx.net wrote: > > > > That's a bunch of non-sense! :) nobody will notice.. If they do then > > > > you show'em who's boss: rmuser * > > > > > > > :-) No, I'm nice to my users. > >Kill them! Kill them all!!! > > > > > Any ideas why it crashed? Could this be a serious bug (4.8-STABLE)? > > > If yes, how do I get a core dump, or at least some more information? > > > I have debug symbols everywhere. It is a clean system, freshly > > > installed a few days ago. > > > I'd really like to know what's going on. > > > > I would suggest using lsof and find out which file the process is > > waiting on. It seems rather strange that the process is in a disk > > wait state for so long. > > > > Marc > >-- > >Best regards, > Chris Did anybody mention Ctrl + Alt + Backsapce to kill the X session? This has worked for me in the past... -- Bob