Date: Tue, 27 Nov 2007 04:18:52 -0800 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Honza Holakovsky <holakac@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Some processes stay active after killing its PID Message-ID: <20071127121852.GA58325@eos.sc1.parodius.com> In-Reply-To: <f996cc420711270405u539d2fccrdbce005d14e88834@mail.gmail.com> References: <f996cc420711260730n1b226483la2b813753f9496f8@mail.gmail.com> <20071126190720.GD19393@slackbox.xs4all.nl> <f996cc420711270405u539d2fccrdbce005d14e88834@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 27, 2007 at 01:05:21PM +0100, Honza Holakovsky wrote: > Thanks for reply, > > I tried to kill the process via all possibilities described in man kill :) > But I didn't know there are some processes which can't be killed, so I tried > again running wdfs, but after "ps -xacu | grep wdfs" I see > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > root 971 73,9 0,9 19048 5552 ?? Rs 1:03od 0:15,36 wdfs > > no D state :( > I'm quite confused, because in state, I have to reboor every time I umount > wdfs drive :( Is it possible to truss or ktrace that process? It would be interesting to know what it's doing (re: chewing up 74% CPU). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | 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?20071127121852.GA58325>