![]() Just open "System Monitor", navigate to the Processes tab, choose the process you want to halt (Hm, could it be the one using 90% CPU?) and right-click it. If you are running a graphical interface, of course, you don't have to fool with this crazy command-line stuff to get the job done. To do so, do kill -KILL pid or kill -9 pid. ![]() So again, only send SIGKILL as a last resort. ![]() This can at times result in data corruption or other problems. But, you should only do so as a last resort, because SIGKILL causes the kernel to terminate the process immediately with no possibility for cleanup. If SIGTERM fails, try SIGHUP, which is stonger medicine: kill -HUP pid. Using kill by itself sends SIGTERM, which you should try first as it allows the program to properly clean up after itself. You might have to use your judgment as to which of the matches needs to be killed, or you could use top instead. Kill pid where pid is the Process ID of the program. The first field of each line of output is a number which represents the Process ID of the program matched by grep (you can safely ignore the last one, which represents grep itself. This should return a line of output that looks something like this: $ ps ax | grep firefoxĢ222 ? S 0:00 /bin/sh /usr/lib/firefox-3.6.9/firefoxĢ231 ? Sl 514:36 /usr/lib/firefox-3.6.9/firefox-binģ0290 pts/2 S+ 0:00 grep -color=auto firefox Open another terminal and run ps ax | grep foo where foo is the name of the unresponsive program.
0 Comments
Leave a Reply. |