From owner-freebsd-stable@FreeBSD.ORG Wed Jun 7 00:24:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCA5816A908 for ; Wed, 7 Jun 2006 00:04:48 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 8553843D48 for ; Wed, 7 Jun 2006 00:04:47 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 07 Jun 2006 00:04:46 -0000 Received: from p509120B8.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.32.184] by mail.gmx.net (mp031) with SMTP; 07 Jun 2006 02:04:46 +0200 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 3927720123D; Wed, 7 Jun 2006 02:04:45 +0200 (CEST) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03033-03; Wed, 7 Jun 2006 02:04:43 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 9F9DA201329; Wed, 7 Jun 2006 02:04:43 +0200 (CEST) From: Matthias Andree To: freebsd-stable@freebsd.org, "Eduardo Meyer" In-Reply-To: (Eduardo Meyer's message of "Tue, 6 Jun 2006 18:16:39 -0300") References: <20060606211327.GG32476@bunrab.catwhisker.org> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Wed, 07 Jun 2006 02:04:43 +0200 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Cc: Subject: Re: How can I know which files a proccess is accessing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2006 00:24:19 -0000 "Eduardo Meyer" writes: > On 6/6/06, David Wolfskill wrote: >> You may find the "lsof" port useful for answering such questions. >> > > I tried it, but it seems that I found some limitations: > > lsof: no local file space at PID 16543 > > # ps 16543 > PID TT STAT TIME COMMAND > 16543 ?? S 0:02.43 /usr/local/sbin/httpd -k start -DSSL > > Any tuning would do the job? Are you running with tightened up security that might prevent fstat from accessing /dev/kmem? I don't know fstat failures from experience or what causes it to just show inode numbers - perhaps delete files that are still open. I'm unsure about the reason for lsof's complaint; if you installed a package, try rebuilding the port. Something different, if fstat and lsof continue to fail: you may try attaching a syscall tracer such as truss, ktrace or strace (the latter from ports) to the process and see if it leaks file descriptors. This may fail due to permissions however. -- Matthias Andree