Istvan, On Sunday 27 November 2005 03:35, Istvan Gabor wrote:

Hello everybody:

Sometimes I can't kill frozen apps with using kill command. Last time amule freezed. What I get after kill:

@linux:~> ps -e |grep amule 15600 pts/2 00:00:51 amule @linux:~> kill 15600 @linux:~> kill 15600 @linux:~> ps -e |grep amule 15600 pts/2 00:00:51 amule @linux:~> kill -9 15600 @linux:~> kill -9 15600 @linux:~> ps -e |grep amule 15600 pts/2 00:00:51 amule @linux:~>

Why is this and how can I stop it w/o rebooting?

Probably the process is in a 'D' wait. Processes in that state cannot be interrupted by a signal, though that signal, if sent, is waiting for the process to come out of the D wait. Show us the output of "ps" with the 'l' option added (look in the STAT column for a D). What kind of file systems do you have installed? I encountered a bug apparently in the ReiserFS code that lead to this symptom (see <https://bugzilla.novell.com/show_bug.cgi?id=129623> for the details). If the problem is a 'D' wait, and the system isn't waiting for a remote resource (are you using NFS or Samba file sharing?), then rebooting is probably the only way to clear the problem. If the problem is remote, it should time out eventually. If it's a local hard drive, then it's certainly a bug and will not time out (D waits should not last more than a fraction of a second), and you should report it. If you think it's another occurrence of the one I reported, attach an addendum to that report, otherwise file a new one. My report has gone unattended since I filed it on October 19th. I'm loathe to run the software that triggered the problem again, even though I need to re-rip my CD collection (the problem occurred while I was running grip).

Thanks, IG

Randall Schulz