From owner-freebsd-questions@FreeBSD.ORG Thu Jan 26 22:33:52 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F328B16A420 for ; Thu, 26 Jan 2006 22:33:51 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B9EC43D48 for ; Thu, 26 Jan 2006 22:33:48 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id k0QMXlam059559; Thu, 26 Jan 2006 16:33:47 -0600 (CST) (envelope-from dan) Date: Thu, 26 Jan 2006 16:33:47 -0600 From: Dan Nelson To: Proniewski Patrick Message-ID: <20060126223346.GH52542@dan.emsphone.com> References: <6F2F4E06-712A-4E3D-9124-7AC7E1B964BD@univ-lyon2.fr> <20060126171333.GB52542@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-questions@freebsd.org Subject: Re: truss and procfs strange problem. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2006 22:33:52 -0000 In the last episode (Jan 26), Proniewski Patrick said: > I have some new details : > > >> $ truss ls > >> truss: cannot open /proc/4509/mem: No such file or directory > > in that case, the command issued as a truss argument (ls, ...) is > stuck in state "D". `man ps` says it "Marks a process in disk (or > other short term, uninterruptible) wait." I think that's this case: parent child ------ ----- call fork() fork() returns (being created) open /proc/%d/mem (fails) (still being created) creation complete, waiting for parent to trace > these process wont be killed, I'll have to reboot. (procctl won't > clear the processes...) You can continue tracing these processes if you run "truss -p ", since that's pretty much what they're waiting for :) -- Dan Nelson dnelson@allantgroup.com