From owner-freebsd-current Sat Jul 24 18:39:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id D497D1500E for ; Sat, 24 Jul 1999 18:39:12 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id UAA06405; Sat, 24 Jul 1999 20:38:12 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199907250138.UAA06405@celery.dragondata.com> Subject: Re: Unkillable processes In-Reply-To: from Kris Kennaway at "Jul 25, 1999 11:04:36 am" To: kkenn@rebel.net.au Date: Sat, 24 Jul 1999 20:38:12 -0500 (CDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got myself two processes which can't be gotten rid of by SIGKILL: > > kkenn 92724 32.0 0.8 5736 356 ?? RN 6:25PM 136:52.96 kvt -T Terminal - > kkenn 1103 0.0 0.0 5740 388 ?? TWN - 0:00.00 (kvt) > > (kvt is the KDE 1.1.1 xterm) > > I am able to trigger this by attempting to paste the contents of a large > buffer from xemacs (v21.1 from ports) into the pico editor from pine4. > > Any ideas before I recompile kvt with -g and try and track down what it's > doing? > > Kris > > For one, do another 'ps' with the 'l' option, so you can see what it's stuck on. The second process is a zombie, which isn't killable until the parent tells it to go away. (Which could very possibly be the first kvt) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message