From owner-freebsd-current@FreeBSD.ORG Sun Feb 8 21:56:04 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 E23CC16A4CE for ; Sun, 8 Feb 2004 21:56:04 -0800 (PST) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2FB143D1D for ; Sun, 8 Feb 2004 21:56:04 -0800 (PST) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.216.114) by smtp01.syd.iprimus.net.au (7.0.024) id 400C4DF400808B02; Mon, 9 Feb 2004 16:57:17 +1100 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id C81A041AE; Mon, 9 Feb 2004 16:55:18 +1100 (EST) Date: Mon, 9 Feb 2004 16:55:18 +1100 From: Tim Robbins To: Matthias Andree Message-ID: <20040209055518.GA64068@cat.robbins.dropbear.id.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: how to confuse truss: truss -f fsck -p / 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: Mon, 09 Feb 2004 05:56:05 -0000 On Mon, Feb 09, 2004 at 04:17:40AM +0100, Matthias Andree wrote: > After typing "truss -f fsck -p /", I see nothing. I press ^Z > and type kill -9 % (killing truss). > > I now have these fine processes hanging dead in memory, they are immune > to kill -9 and don't respond to kill -CONT either, ps axl: > > UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND > 0 56974 1 0 8 0 1256 744 ppwait D p1 0:00.00 fsck -p / > 0 56975 56974 0 8 0 1256 744 stopev DV p1 0:00.00 fsck -p / > > Is this how things are supposed to be, even though killing a tracer is > way stupid? I think it's not nice to have unkillable processes. procfs is disabled by default for a reason :-) > Is there a way to get rid of these without reboot? Try procctl(8). Tim