From owner-freebsd-questions Wed Dec 6 14:26:19 2000 From owner-freebsd-questions@FreeBSD.ORG Wed Dec 6 14:26:17 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from cheshire.manunkind.org (cheshire.manunkind.org [216.254.114.213]) by hub.freebsd.org (Postfix) with ESMTP id 610FC37B400 for ; Wed, 6 Dec 2000 14:26:04 -0800 (PST) Received: (from ryan@localhost) by cheshire.manunkind.org (8.11.1/8.11.1) id eB6MVpY20162; Wed, 6 Dec 2000 17:31:51 -0500 (EST) (envelope-from ryan) Date: Wed, 6 Dec 2000 17:31:51 -0500 From: Ryan Younce To: Joe Oliveiro Cc: Ryan Younce , Corey Brune , freebsd-questions@FreeBSD.ORG Subject: Re: Process wont be killed. Message-ID: <20001206173151.A20117@cheshire.manunkind.org> References: <20001206160200.A19885@cheshire.manunkind.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from joe@advancewebhosting.com on Wed, Dec 06, 2000 at 04:36:26PM -0500 Sender: ryan@cheshire.manunkind.org Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Joe Oliveiro : > I've encounted times where there was a single apache child/parent process > running which could not be killed. A reboot would cause the system to hang > because the process could not be killed. That only happens once in a while > tho. There was something going around on hackers a couple of years ago concerning processes which, even when signalled with SIGKILL, would not die if they were in the middle of an I/O operation via a slow FS (like NFS under certain situations). Netscape Enterprise Server (bleh) did the same thing on Solaris, and without NFS, before Sun patched it. I doubt this is the same thing, though. In any event, killing the child will have no effect. -- Ryan Younce | "Well it's worked so far but we're not out yet." ryan@manunkind.org | --DeForest Kelley (Dr. Leonard McCoy) www.manunkind.org/~ryan/ | "I, Mudd," Star Trek TOS Prod No 41 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message