Some processes stay active after killing its PID
Honza Holakovsky
holakac at gmail.com
Tue Nov 27 04:05:24 PST 2007
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 :(
2007/11/26, Roland Smith <rsmith at xs4all.nl>:
>
> On Mon, Nov 26, 2007 at 04:30:01PM +0100, Honza Holakovsky wrote:
> > Hi,
> >
> > I'm expecting quite curious problem (currently spotted with usage of
> > audacious (1.3.2 [20070405-4320]) and fusefs-wdfs (1.3.2))
> > After I finish working with either of these two programs (i.e. closing
> > audacious windown or unmounting wdfs unit), they still run on
> background,
> > and cosume all remaining cpu performance. Even if I kill its PID, it's
> still
> > running. "top" looks like this:
>
> How did you kill them? Did you use 'kill -9'?
>
> > last pid: 21161; load averages: 1.30, 1.33, 1.11
> > up 0+02:49:43 16:20:56
> > 51 processes: 3 running, 48 sleeping
> > CPU states: 53.1% user, 0.0% nice, 46.5% system, 0.4% interrupt,
> 0.0%idle
> > Mem: 209M Active, 226M Inact, 105M Wired, 21M Cache, 70M Buf, 54M Free
> > Swap: 2048M Total, 20K Used, 2048M Free
> >
> > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU
> COMMAND
> > 19163 root 1 132 0 19112K 4948K RUN 14:57 81.88% wdfs
> > 18873 holakac 1 96 0 79652K 53568K select 13:14 1.66% Xorg
> > 18911 holakac 4 20 0 104M 81280K kserel 9:06
> 0.00%firefox-bin
>
> Under some circumstances, a process cannot be killed, e.g. if 'px -xacu'
> has the process in D state. See ps(1).
>
> 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)
>
>
More information about the freebsd-stable
mailing list