The process that will not die

[columb]

I'm getting (and have been for over an hour)

root@b04601:/#ps -ef | grep 4976[2]
       -  49762      -   -                     - <exiting>
  patrol  61766  49762   0                  0:00 <defunct>
  patrol 206434  49762   5                  0:00 <defunct>
  patrol 217498  49762   6                  0:42 <defunct>
  patrol 442994  49762   0                  0:00 <defunct>

Any ideas what I should do to clear this up?

Ceci n'est pas une signature
Columb Healy

 

[TSch]

Hi,

have you already tried a

kill -9 "process number"

especially on the 49762 ?

Regards
Thomas

 

[columb]

We tried various levels of kill, ending up with -9. That's when the trouble started

Ceci n'est pas une signature
Columb Healy

 

[RodKnowlton]

If there's a file that those processes have open (and no processes you care about also have it open), I've had luck in the past using "fuser -k" to get rid of a process that I couldn't otherwise kill.

I say "luck" because it doesn't always work.

- Rod


IBM Certified Advanced Technical Expert pSeries and AIX 5L
CompTIA Linux+
CompTIA Security+

A Simple Code for Posting on the Web

 

[columb]

Thanks for the tip, Rod, but no luck this time. I guess we'll have to wait for the next reboot. there's a memory upgrade due in the next few weeks so hopefully it won't be long.

Ceci n'est pas une signature
Columb Healy

 

[khalidaaa]

These are Zombie processes!

ps –auw | grep defunct Shows zombies processes (to kill – reboot or kill the parent)

Your best bet is to kill the parent process, 49762. The defunct process might die; but if it's parent process becomes init ( PID 1 ) you will have to wait for a reboot.

As long as the PPID is not 1 or init; you might be able to kill it by sniping the parent process.

Found these comments while surfing the internet!

Regards,
Khalid