From owner-freebsd-questions@FreeBSD.ORG  Tue Jul 15 13:29:02 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 E97CC37B401
	for <freebsd-questions@freebsd.org>;
	Tue, 15 Jul 2003 13:29:02 -0700 (PDT)
Received: from mx0.gmx.net (mx0.gmx.de [213.165.64.100])
	by mx1.FreeBSD.org (Postfix) with SMTP id 9E7A443F75
	for <freebsd-questions@freebsd.org>;
	Tue, 15 Jul 2003 13:29:01 -0700 (PDT)
	(envelope-from daniela5743@gmx.net)
Received: (qmail 9506 invoked by uid 0); 15 Jul 2003 20:29:00 -0000
Date: Tue, 15 Jul 2003 22:29:00 +0200 (MEST)
From: daniela5743@gmx.net
To: dick hoogendijk <dick@nagual.st>
MIME-Version: 1.0
References: <20030715201215.GA24697@lothlorien.nagual.st>
X-Priority: 3 (Normal)
X-Authenticated-Sender: #0008958870@gmx.net
X-Authenticated-IP: [212.33.58.27]
Message-ID: <10321.1058300940@www21.gmx.net>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
cc: freebsd-questions@freebsd.org
Subject: Re: KDE process is unkillable
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2003 20:29:03 -0000

> On 15 Jul daniela5743@gmx.net wrote:
> > I tried it multiple times. I was able to kill all the other KDE
> > related processes (even the parent), but this one just doesn't die.
> 
> Then kill (-9) the login session itself (the one kde came from in the
> first place)
> 
> And if that too does not help: a home server is very easely rebooted.
> Nobody will notice or at least hardly..

Thanks for the advice, but I really don't want to kick my users off.
If it is really necessary, I want to get a core dump before rebooting.
Do you know how I could do this?

I'm trying to install lsof, but it takes forever (KDE takes up all the CPU
time).
Here's the output from fstat, maybe this solves the problem:

root     kdeinit    62100 root /             2 drwxr-xr-x     512  r
root     kdeinit    62100   wd /usr     6690817 drwxr-xr-x    2048  r
root     kdeinit    62100 text /usr     341416 -r-xr-xr-x  412176  r
root     kdeinit    62100    0 /         65411 crw-------   ttyv3 rw
root     kdeinit    62100    1 /         65411 crw-------   ttyv3 rw
root     kdeinit    62100    2 /         65411 crw-------   ttyv3 rw
root     kdeinit    62100    7 /         64909 crw-rw----  #C145:0 rw
root     kdeinit    62100    8* pipe e390a2a0 <-> e390a520      0 rw
root     kdeinit    62100    9* pipe e390a520 <-> e390a2a0      0 rw
root     kdeinit    62100   10* pipe df266260 <-> df2652c0      0 rw
root     kdeinit    62100   11* pipe df2652c0 <-> df266260      0 rw

-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++

Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern!