Date: Tue, 27 Sep 2011 03:10:08 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Nikos Vassiliadis <nvass@gmx.com> Cc: freebsd-stable@freebsd.org Subject: Re: non-responding processes after truss(1)ing Message-ID: <20110927101008.GA27810@icarus.home.lan> In-Reply-To: <4E819DF7.3060306@gmx.com> References: <4E819DF7.3060306@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110927101008.GA27810>