non-responding processes after truss(1)ing

2011-09-27 Thread Nikos Vassiliadis
Hi, 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

Re: non-responding processes after truss(1)ing

2011-09-27 Thread Jeremy Chadwick
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

Re: non-responding processes after truss(1)ing

2011-09-27 Thread Nikos Vassiliadis
On 9/27/2011 1:10 PM, Jeremy Chadwick wrote: 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

Re: non-responding processes after truss(1)ing

2011-09-27 Thread Mark Saad
On Tue, Sep 27, 2011 at 6:19 AM, Nikos Vassiliadis nv...@gmx.com wrote: On 9/27/2011 1:10 PM, Jeremy Chadwick wrote: 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

Re: non-responding processes after truss(1)ing

2011-09-27 Thread Jeremy Chadwick
On Tue, Sep 27, 2011 at 09:28:56AM -0400, Mark Saad wrote: On Tue, Sep 27, 2011 at 6:19 AM, Nikos Vassiliadis nv...@gmx.com wrote: On 9/27/2011 1:10 PM, Jeremy Chadwick wrote: kill -9 your truss processes; the underlying processes which you are truss'ing will probably resume. My