From owner-freebsd-questions Thu Jan 23 7:42:12 2003 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 5289937B401 for ; Thu, 23 Jan 2003 07:42:11 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD75843ED8 for ; Thu, 23 Jan 2003 07:42:10 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.6/8.12.6) id h0NFgAlP093333; Thu, 23 Jan 2003 09:42:10 -0600 (CST) (envelope-from dan) Date: Thu, 23 Jan 2003 09:42:10 -0600 From: Dan Nelson To: Oliver Fromme Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Cannot kill truss process Message-ID: <20030123154210.GA83066@dan.emsphone.com> References: <20030123153024.GC53550@dan.emsphone.com> <200301231537.h0NFboRc012209@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200301231537.h0NFboRc012209@lurza.secnetix.de> X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.3i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Jan 23), Oliver Fromme said: > Dan Nelson wrote: > > In the last episode (Jan 23), Oliver Fromme said: > > > I've got a problem on a 4.7-RELEASE machine. I tried using > > > /usr/bin/truss on a process (which was running in a chroot > > > environment, which in turn is on an NFS-mounted filesystem, > > > if that matters). But now I cannot kill the truss process > > > itself anymore, it's hanging there for a few days already. > > > > Do a ps axlp 65275; what's the WCHAN column say? > > It says "stopev": > > # ps lwwp 65275 > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > 1011 65275 1 0 10 0 268 136 stopev D pd- 0:00.00 truss jws -2 (jws) That looks like truss was being trussed :) I thought "stopevent" was what traced processes stopped at while the tracing process was working on them. Try running "truss -p 65275" and see if it frees up. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message