From owner-freebsd-current  Sun Jul 25  7:59: 3 1999
Delivered-To: freebsd-current@freebsd.org
Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.6.3])
	by hub.freebsd.org (Postfix) with ESMTP id 34A5E15199
	for <current@freebsd.org>; Sun, 25 Jul 1999 07:58:57 -0700 (PDT)
	(envelope-from bf20761@binghamton.edu)
Received: from localhost (bf20761@localhost)
	by bingsun1.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id KAA01856;
	Sun, 25 Jul 1999 10:56:58 -0400 (EDT)
X-Authentication-Warning: bingsun1.cc.binghamton.edu: bf20761 owned process doing -bs
Date: Sun, 25 Jul 1999 10:56:58 -0400 (EDT)
From: Zhihui Zhang <bf20761@binghamton.edu>
X-Sender: bf20761@bingsun1
To: Grey Lehey <grog@lemis.com>
Cc: current@freebsd.org
Subject: Re: Unkillable processes
In-Reply-To: <Pine.GSO.3.96.990725102358.15970B-100000@sol.cs.binghamton.edu>
Message-ID: <Pine.GSO.BU-L4.10.9907251038310.1524-100000@bingsun1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> No.  You can't kill a process which is in kernel mode.  If it doesn't
> come out, you won't be able to stop it.  It seems rather unlikely that
> that's the case here, though.

It seems to me that a process can only suicide after it detects somebody
wants to kill it.  Anyway, it is the process itself that calls exit(). A
process must be runnable to be killed (actually suicide). Am I right?

-Zhihui




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message