From owner-freebsd-current@FreeBSD.ORG Fri Feb 13 10:39:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F75716A4CE for ; Fri, 13 Feb 2004 10:39:08 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 047C643D2F for ; Fri, 13 Feb 2004 10:39:08 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i1DId4ZV051641; Fri, 13 Feb 2004 13:39:04 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i1DId3ak051638; Fri, 13 Feb 2004 13:39:04 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Fri, 13 Feb 2004 13:39:03 -0500 (EST) From: Andre Guibert de Bruet To: Wade Klaver In-Reply-To: <200402130923.49142.archeron@wavefire.com> Message-ID: <20040213133811.S34361@alpha.siliconlandmark.com> References: <200402130923.49142.archeron@wavefire.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: Creating unkillable processes. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 18:39:08 -0000 On Fri, 13 Feb 2004, Wade Klaver wrote: > Hello folks, > I am somehow managing to create an unkillable process. It is a javavm > instance run by an unprivileged user. It happens (most of the time) when I > do the following: > killall java (a few times when the process is in the state "kserel") > killall -TERM java (again a few times) > killall -9 java > After the attempt to send a SIGKILL, the process the goes into the WAIT state > according to top. At this point the process ignores all signals, even from > root, and can only be killed with a reboot. > If I can provide any additional information, please let me know. Below is the > system CV. What scheduler are you using? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >