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 | _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"