Some processes stay active after killing its PID

[Honza Holakovsky]

Well, didn't know that, "/bin/kill -9 wdfs_PID" works, great

Thanks a lot, after your advice I read an article about csh built-in
commands, never heard of it from any fbsd handbook...

2007/11/27, Roland Smith <rsmith at xs4all.nl>:
>
> 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 :(
>
> By default, the shell uses it's built-in kill function. Try invoking the
> real
> kill directly, as root; '/bin/kill -9 971'
>
> Roland
> --
> R.F.Smith                                   http://www.xs4all.nl/~rsmith/
> [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
> pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
>
>