From owner-freebsd-stable@FreeBSD.ORG Tue Sep 27 10:10:09 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36A9F1065673 for ; Tue, 27 Sep 2011 10:10:09 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by mx1.freebsd.org (Postfix) with ESMTP id 201168FC0C for ; Tue, 27 Sep 2011 10:10:08 +0000 (UTC) Received: from omta24.emeryville.ca.mail.comcast.net ([76.96.30.92]) by qmta15.emeryville.ca.mail.comcast.net with comcast id dlu91h0021zF43QAFmA2ko; Tue, 27 Sep 2011 10:10:02 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta24.emeryville.ca.mail.comcast.net with comcast id dmAj1h0071t3BNj8kmAjTH; Tue, 27 Sep 2011 10:10:43 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 558EC102C19; Tue, 27 Sep 2011 03:10:08 -0700 (PDT) Date: Tue, 27 Sep 2011 03:10:08 -0700 From: Jeremy Chadwick To: Nikos Vassiliadis Message-ID: <20110927101008.GA27810@icarus.home.lan> References: <4E819DF7.3060306@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E819DF7.3060306@gmx.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: non-responding processes after truss(1)ing 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: Tue, 27 Sep 2011 10:10:09 -0000 On Tue, Sep 27, 2011 at 12:57:11PM +0300, Nikos Vassiliadis wrote: > My system have two non-responding processes after some truss(1)ing > i did on them. They seem stopped and do not respond to sigcont. > > >%ps > > PID TT STAT TIME COMMAND > > 9768 0- I 0:00.12 truss -p 9739 > > 9514 1 Is 0:00.29 -csh (csh) > > 9739 1 TX+ 2:06.24 sqlite3 ../nikos_output_actives.tst/database.db > > 7821 4- TX+ 0:33.62 python active.py > > 7828 4- I 0:00.57 truss -p 7821 > > 9848 5 Ss 0:00.23 -csh (csh) > >10053 5 R+ 0:00.00 ps > >% > > it's not actually 8.2-STABLE, but 8.2-RELEASE-p1, are there any > fixes in -STABLE regarding this problem? kill -9 your truss processes; the underlying processes which you are truss'ing will probably resume. My experience for years has been that truss on FreeBSD is extremely buggy and cannot be relied upon (case in point). Such is still the case on RELENG_8 as of today. Use ktrace(1) instead. You'll find it to work pretty much in every situation. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |