I received two suggestions to this problem, but none of them simple. :-(
#1 from Rich Copeland:
> Use fuser and see what it has locks into ... there is something locking here, the only reason I have ever seen a process not die is generally because of a locking issue.
#2 from John Lanier
> Hello,
>
> Once this process gets in this state and kill -9/-HUP doesn't work,
> either a reboot or the following procedure are pretty much your only options
> (NOTE: use this procedure with caution, as killing PIDs that are multi-threaded
> can have strange, undesirable affects on the system involved):
>
> PURPOSE :
>
> If 'kill pid', 'kill -15 pid' or 'kill -9 pid' don't
> get rid of a defunct process, you can use the kdbx utility
> to stop the process.
>
> The process may be waiting for a signal before it ends.
> Take care in making sure you know which process needs to
> be killed.
>
> You can use kdbx to stop it.
>
> Be very careful that there are no typographical errors
> while in kdbx, and that you have the correct pid.
>
>
> # ps aux
> Find the 'pid' of the process you want killed.
>
> # kdbx -k /vmunix
> dbx version 3.11.10
> Type 'help' for help.
>
> stopped at [thread_block:2097 ,0xfffffc00002a86c0]
> Source not available
> warning: Files compiled -g3: parameter values probably wrong
>
> (kdbx) set $pid=<the pid you want to stop>
> for example: (kdbx) set $pid=777
>
> (kdbx) p (*(struct super_task *)thread.task) .proc.p_stat
> 3 <this is the response. the number may not be '3'
>
> (kdbx) a (*(struct super_task *)thread.task) .proc.p_stat=0
> 0
> (kdbx) u
>
>
> **********
Thanks!
Fernando
Received on Mon Nov 24 2003 - 19:15:21 NZDT