From owner-freebsd-current@FreeBSD.ORG Sat Jan 15 16:30:09 2005 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 2AD2716A4CE for ; Sat, 15 Jan 2005 16:30:09 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA7BF43D48 for ; Sat, 15 Jan 2005 16:30:08 +0000 (GMT) (envelope-from bsdaemon@comcast.net) Received: from fw.home (pcp05404374pcs.norstn01.pa.comcast.net[68.80.144.252]) by comcast.net (sccrmhc12) with SMTP id <20050115163008012000u5ibe>; Sat, 15 Jan 2005 16:30:08 +0000 Received: (qmail 87773 invoked from network); 15 Jan 2005 16:30:06 -0000 Received: from kris.home (HELO ?192.168.0.251?) (192.168.0.251) by fw.home with SMTP; 15 Jan 2005 16:30:06 -0000 Message-ID: <41E94650.2060609@comcast.net> Date: Sat, 15 Jan 2005 11:35:28 -0500 From: Kris Maglione User-Agent: Mozilla Thunderbird 1.0 (X11/20041212) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20050112092641.GA61635@stud.fit.vutbr.cz> <20050115134715.GA769@zaphod.nitro.dk> In-Reply-To: <20050115134715.GA769@zaphod.nitro.dk> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: non-killable process 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: Sat, 15 Jan 2005 16:30:09 -0000 Simon L. Nielsen wrote: >On 2005.01.12 10:26:41 +0100, Divacky Roman wrote: > > >>hi, >> >>I have CFLAGS=-Os (dunno if it matters) compiled ports/net/iftop. and whenever >>I run it on recent 6-current it "hangs": >> 880 v4 R+ 0:00.05 iftop >>(ps ax output) >> >>and it cannot be killed - I can repeat it, so this might reveal some bug. I use >>sched_ule. >> >From http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/basics-daemons.htm SIGKILL can not be ignored by a process. This is the ``I do not care what you are doing, stop right now'' signal. If you send SIGKILL to a process then FreeBSD will stop that process there and then[1]. [1] Not quite true--there are a few things that can not be interrupted. For example, if the process is trying to read from a file that is on another computer on the network, and the other computer has gone away for some reason (been turned off, or the network has a fault), then the process is said to be ``uninterruptible''. Eventually the process will time out, typically after two minutes. As soon as this time out occurs the process will be killed.