может кому пригодитсяIf you can't kill a process (even with SIGKILL), it means
that the process currently can't be put on the run queue,
because only processes that are able to run can receive
signals. Given that, such a situation usually has one of
these three reasons:
1. The process hangs in "disk wait" (flag "D" in ps' STAT
column). This often means there's a hardware problem
with your disk or controller (or a driver bug), or a
network problem if you use NFS.
2. The process was suspended (SIGSTOP). In this case
there is the flag "T" in ps' STAT column. Try sending
a SIGCONT to the process.
3. The process terminated, but the parent process failed
to pick up the exit code. In this case, the process
needs to retain an entry in the process table (shown
by ps) in order to record the exit code until it is
picked up, even though the process itself is gone.
Such a "dead" entry in the process table is called a
zombie process. In ps' STAT column there is the "Z"
flag. This usually indicates a programming error
(a.k.a. bug) in the parent process. You can get rid
of the zombie by killing the parent process. Then the
zombie will be inherited by the next process in the
hierarchy (up to the init process 1 if required) which
will then pick up the exit code and release the process
entry.
There can be other reasons on occasion, but those three are
the most common ones. Simply look at the STAT column in
the ps(1) output for the process in question. It will tell
you the reason why the process is stuck.
Best regards
Oliver
http://lists.freebsd.org/pipermail/free ... 82821.html
наверняка многие, из посетителей форума, сталкивались с ситуациями когда процесс не получалось завершить вручную, помогала лишь перезагрузка
вышеприведенный комментарий как раз затрагивает эти ситуации
