Date: Thu, 23 Jan 2003 09:42:10 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Oliver Fromme <olli@secnetix.de> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Cannot kill truss process Message-ID: <20030123154210.GA83066@dan.emsphone.com> In-Reply-To: <200301231537.h0NFboRc012209@lurza.secnetix.de> References: <20030123153024.GC53550@dan.emsphone.com> <200301231537.h0NFboRc012209@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 23), Oliver Fromme said: > Dan Nelson <dnelson@allantgroup.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030123154210.GA83066>