topic Re: Kill running process in Operating System - HP-UX

Kill running process

Patricia_2 — Wed, 16 Aug 2000 00:15:53 GMT

Hi,

I'm using command kill -9 PID to kill one of my running process.Unfortunely the process still running.

I try to kill the Shell PID to disconnect the session, unfortunely the process still running ,but the session is actually disconnected.

Please guide and Thanks in advance.

Regards,
Pat

Re: Kill running process

Philip Chan_1 — Wed, 16 Aug 2000 00:36:31 GMT

Does the user who issue the "kill -9" command have sufficient authority to do so?

Rgds
Philip

Re: Kill running process

Patricia_2 — Wed, 16 Aug 2000 00:46:33 GMT

I'm using root user id to run the kill command

Re: Kill running process

Philip Chan_1 — Wed, 16 Aug 2000 01:03:14 GMT

I seem before that de-functioned processes cannot be terminated by kill -9 command, in that case I had to kill their parent process in order to get rid of them.

What was the status for your process?

Re: Kill running process

Patricia_2 — Wed, 16 Aug 2000 01:09:41 GMT

Hi Chan,

I have kill the parent pid , and this cause the PPID for the process become 1.

Re: Kill running process

Anthony Goonetilleke — Wed, 16 Aug 2000 05:09:22 GMT

if it is owned by 1 it means it is a child of init. Usually a reboot is needed to get rid of these runaway proc's

Re: Kill running process

Stefan Farrelly — Wed, 16 Aug 2000 06:17:54 GMT

This process must now be stuck on a socket. Theres no easy to free up a stuck socket under HP-UX. The only options are to;

1. reboot the PC or WS that the user was using who started the process. This may free up the stuck socket allowing the process to die. (give it some time after the reboot before moving onto option 2.)
2. reboot the HP server.

Re: Kill running process

Andy Monks — Wed, 16 Aug 2000 06:20:25 GMT

Kill -9, should be the last resort not the first.

However, all kills can fail (including -9), if the process is waiting on a system call that is uninterruptable. There is no way to kill/remove these processes if what the system call is waiting for, is missed or never turns up. Only a reboot will clear them.

Kill -9 however, can make things worse, as it doesn't give the process enough time to tidy up. It won't release shared memory, semaphores, file locks etc, and you can be heading for a reboot due just to doing a kill -9.

If a process won't die with a kill -15 or -1, then try and see if it's still running before doing a -9. If it's 'sleeping' don't using -9, as it's not going to die anyway. If it's running, then someone is just trapping the signals and -9 will probably kill it. However, as I stated above, the process won't clean up after it's self.

Btw, you can't trap kill -9.

Re: Kill running process

Horst Prestin — Wed, 16 Aug 2000 06:27:36 GMT

Sometimes if I have such a "zombie" I have to reboot.
This really helps.

Re: Kill running process

Philip Chan_1 — Wed, 16 Aug 2000 06:36:40 GMT

Can we awake a sleeping process by kill -26 (SIGCONT) and hope it catch the abort signal from the OS?

-Philip

Re: Kill running process

Patricia_2 — Wed, 16 Aug 2000 06:43:58 GMT

I try to kill the process by using the kill -26, but the process still there.

I think the only way is to reboot.

Anywhere thanks for advise.

Regards,
Pat

Re: Kill running process

dan mcelroy — Sat, 19 Aug 2000 12:54:50 GMT

We have ran into simular process that will not allow kill -9. We put into a script a trap and three consective kills -9's. this works sometimes, and if not working the first time, we do it again...so far, it hasn't failed on the second attempt.