Date: Thu, 23 Jan 2003 16:55:50 +0100 (CET) From: Oliver Fromme <olli@secnetix.de> To: freebsd-questions@FreeBSD.ORG Subject: Re: Cannot kill truss process Message-ID: <200301231555.h0NFtoQF013170@lurza.secnetix.de> In-Reply-To: <20030123154210.GA83066@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson <dnelson@allantgroup.com> wrote: > 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 - > > 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. # truss -p 65275 SIGNAL 9 SIGNAL 9 process exit, rval = 9 Killed # ps lwwp 65275 UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND # Hooray! Thanks a bunch! :) Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) 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?200301231555.h0NFtoQF013170>