[opensuse] Help Killling Process
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Donald D Henson wrote:
I remember from the 'old days' that there is a cli command to identify a process id $ ps auxf | grep firefox | grep <your_user_name>
and another one to kill a process. $ kill <pid>
or, if it fails to die $ kill -9 <pid> There is also a "killall" command that you can use with the process name, but it may be more indiscriminate. "man killall" is your friend ;-) HTH Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com <http://www.iba-worldwide.com> The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated. Try ctrl-alt-Esc. That brings up a skull and crossbones. Click it in
On Tue, 20 Mar 2007 10:58:42 -0600 Donald D Henson <wepin@wepin.com> wrote: the offending window and you will kill the process. From the command line: ps ax | grep -i firefox then kill -9 <process -id> Normally I use kill -TERM first, and if that does not kill the process, then use -9. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
Jerry Feldman wrote:
On Tue, 20 Mar 2007 10:58:42 -0600 Donald D Henson <wepin@wepin.com> wrote:
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
Try ctrl-alt-Esc. That brings up a skull and crossbones. Click it in the offending window and you will kill the process.
From the command line: ps ax | grep -i firefox then kill -9 <process -id>
Normally I use kill -TERM first, and if that does not kill the process, then use -9.
How about in KDE <CTRL><ALT><ESC> which brings up a skull and crossbow. However over the GUI you want killed and press the left mouse button. Bob
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 20 March 2007 12:56, Robert Lewis wrote:
Jerry Feldman wrote:
On Tue, 20 Mar 2007 10:58:42 -0600
Donald D Henson <wepin@wepin.com> wrote:
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
Try ctrl-alt-Esc. That brings up a skull and crossbones. Click it in the offending window and you will kill the process.
From the command line: ps ax | grep -i firefox then kill -9 <process -id>
Normally I use kill -TERM first, and if that does not kill the process, then use -9.
How about in KDE <CTRL><ALT><ESC> which brings up a skull and crossbow. However over the GUI you want killed and press the left mouse button.
Bob
That is last resort as it performs kill -9 <pid> which is instruction to kernel to terminate process, which doesn't allow process to save status, like kill <pid> # this actually performs the same as next lines kill -15 <pid> kill -TERM <pid> that is signal to process that is time to quit. If after that some minute or so, application doesn't exit, and you have reasons to believe, like in above example, that it doesn't work than apply skull and crossed bones, or kill -9 <pid> -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Donald D Henson wrote:
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
It probably doesn't actually have a process running. It sees the file ~/.mozilla/firefox/05uz5zzz.default/.parentlock and thinks it is still running (so even a reboot might not fix it). If you don't actually see a firefox process, try deleting that file (using, of course, your own special .default folder). -- Jonathan Arnold (mailto:jdarnold@buddydog.org) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ UNIX is user-friendly. It's just a bit picky about who its friends are. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Donald, On Tuesday 20 March 2007 09:58, Donald D Henson wrote:
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.)
By which you mean it has something to do with the Flash plug-in, which YouTube uses to display all its video (that's there "innovation").
When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
The command "pidof" tells the process IDs for all running instances of a given executable. (You should know that Firefox's executable binary is called "firefox-bin", not "firefox".) The command "ps" lists running processes. By default, it lists only those started by you and associated with the same terminal from which the ps command was issued. If you add the "-a" option, it will show all of your processes that are associated with some tty (which still excludes most GUI processes). Using "ps -u yourLoginNameOrUserID" will show all of your processes without regard to controlling tty. Using "ps -ax" will show all processes running on the system, regardless of who started them or whether they have a controlling tty. Kill is the command that sends signals to processes. The default signal sent by kill, SIGTERM, or 15, is a polite request for a process to shut down. It gets to perform whatever clean-up processing it requires. By the same token, the process can ignore such a request. The unignorable kill signal (SIGKILL or 9) cannot be intercepted by the process in order to perform clean-up operations (or to refuse to die), so it will kill the process if at all possible. It's never preferable to use SIGKILL, at least not before trying SIGTERM. Kill exists as a shell built-in, so you can use "help kill" to get usage information. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 20 March 2007 11:58, Donald D Henson wrote:
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
Hi Donald. To identify a process and extract its Process ID (PID,) use the 'ps' command: ps -eaf|grep <enter name of process here> This will list any currently running processes with the name specified The brackets are there to for context. Don't include them in the command. The output from this command will list the PIDs of the matching processes and the PIDS of the parents of those processes - like this: $ ps -eaf|grep xterm jvollmer 30239 30215 0 12:07 pts/2 00:00:00 xterm jvollmer 30257 30215 0 12:07 pts/2 00:00:00 grep xterm (the first number for each process is the PID, the second is the PID of the parent) Locate the PID for the process you wish to terminate and use the 'kill' command: kill -9 <PID> Again, the brackets are there for context. Don't include them in your command. To kill the xterm process in the above example, use the command: kill -9 30239 This command sends a specified signal number to the process identified by PID. The signal is a number between 1 and 64. Number 9 means kill the process Identified by <PID>. For a complete list of available signals, type: kill -l For more information, see the man pages for 'ps' and 'kill.' -- JAY VOLLMER JVOLLMER@VISI.COM TEXT REFS DOUBLEPLUSUNGOOD SELFTHINK VERGING CRIMETHINK - IGNORE FULLWISE -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 20 March 2007 10:28, Jay C Vollmer wrote:
...
Note that in most cases, this approach will find the grep process, too. "Pidof" is the direct way to find process IDs as such.
The output from this command will list the PIDs of the matching processes and the PIDS of the parents of those processes - like this:
$ ps -eaf|grep xterm jvollmer 30239 30215 0 12:07 pts/2 00:00:00 xterm jvollmer 30257 30215 0 12:07 pts/2 00:00:00 grep xterm
(the first number for each process is the PID, the second is the PID of the parent)
Another reason that "ps" is less than ideal for this purpose. There are too many similar numbers in the output and when you filter ps output with grep, you don't see the column headers. If you send the signal to the process group (the other number right next to the PID), you'll not get the results you want and you probably will not like the results you get.
Locate the PID for the process you wish to terminate and use the 'kill' command:
kill -9 <PID>
Absolutely a bad idea. Many programs have clean-up operations to perform. This guarantees those clean-up actions will not take place. Signal TERM or 15 is the clean way to kill a process. Only resort to KILL or 9 when TERM does not cause the process to terminate.
...
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 20 March 2007 12:37, Randall R Schulz wrote:
kill -9 <PID>
Absolutely a bad idea. Many programs have clean-up operations to perform. This guarantees those clean-up actions will not take place.
Signal TERM or 15 is the clean way to kill a process. Only resort to KILL or 9 when TERM does not cause the process to terminate. Yup, except that what we are talking about here is a process that won't die... kill -9 <PID> is the ONLY way to get it to happen.
Another way to say this is that if SIGTERM will kill the process then you probably didn't need to be in an xterm window running the kill command in the first place. The usual reason for a process to "refuse to die" is that it is no longer correctly performing signal handling, so giving it the SIGTERM is useless. kill -9 <PID> is the only way to go in these situations. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 20 March 2007 12:37, Randall R Schulz wrote:
kill -9 <PID>
Absolutely a bad idea. Many programs have clean-up operations to perform. This guarantees those clean-up actions will not take place.
Signal TERM or 15 is the clean way to kill a process. Only resort to KILL or 9 when TERM does not cause the process to terminate. Yup, except that what we are talking about here is a process that won't die... kill -9 <PID> is the ONLY way to get it to happen.
Another way to say this is that if SIGTERM will kill the process then you probably didn't need to be in an xterm window running the kill command in the first place. The usual reason for a process to "refuse to die" is that it is no longer correctly performing signal handling, so giving it the SIGTERM is useless.
kill -9 <PID> is the only way to go in these situations. The difference is that SIGTERM is a catchable signal, and should generally be tried first because the process can clean itself up. If
On Tue, 20 Mar 2007 13:17:52 -0500 M Harris <harrismh777@earthlink.net> wrote: that does not work, then by all means use SIGKILL (-9) as it is not catchable by the process. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
Le Mardi 20 Mars 2007 17:58, Donald D Henson a écrit :
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
Hi, You could use "ps -d" to identify the process and then kill it "kill PID" or "kill -KILL PID". You might have to be root to be able to kill the process. Another way (especially with an unknown process eating CPU) is to launch top "top", press K and then enter the PID of the CPU eating process. -- __________________________________________________________ Matthias Titeux, PhD Département de génétique des maladies cutanées et allergiques dans des modèles animaux et chez l'homme. INSERM U563 - CPTP Pavillon Lefebvre, 5ème étage CHU Purpan BP3028 31024 Toulouse cedex 03 __________________________________________________________ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
What a rapid response from so many. The best part is that most of the advice is consistent. It seems that I have been dealing with the GUI too much. I should use the CLI more often. Thanks for all the help. Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules Donald D Henson wrote:
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
What a rapid response from so many. The best part is that most of the advice is consistent. It seems that I have been dealing with the GUI too much. I should use the CLI more often. Thanks for all the help. The CLI (eg. the shells) are always available in Linux and Unix systems. The GUI simply sits on top of the system. This is one reason why we can have many different GUI's on Linux. One little trick we use on occasion is if for some reason the GUI hangs and we can't get a response, we can log in via the network and simply kill the GUI. Both KDE and GNOME have matured enough that it is rare to experience a lockup. Just remember that most Linux systems have 6 virtual terminals
On Tue, 20 Mar 2007 15:12:13 -0600 Donald D Henson <wepin@wepin.com> wrote: that are totally independent of the GUI. Each virtual terminal corresponds to a function key (F1 - F6). F7 is used for the first session, and you can even have multiple GUI sessions. When I teach my Linux course, I generally have both KDE and GNOME running. In contrast, Windows NT does not have an underlying CLI. The command prompt runs as a subordinate process. The down side of Linux is that you have so many choices it can be overwhelming, especially for new users. Since I have a degree from Burger King's Whopper College (this is true) I tend to prefer the "have it your way" approach rather than the "you can have any color you want as long as it is black". -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
Donald D Henson wrote: Hi Donald,
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
I think the command you are looking for is 'top' ie executed from an unprivleged user: $> top This will give you a listing of the processes and their pid' although with the update frequency set high, it is difficult to identify the correct pid as the lines of the displayed processes keep changing. Rather use one of the other post' recommendations. Regards Hylton P.S: Please respond to opensuse@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2007-03-24 at 14:51 +0200, Hylton Conacher (ZR1HPC) wrote:
Donald D Henson wrote:
Hi Donald,
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
I think the command you are looking for is 'top' ie executed from an unprivleged user: $> top
This will give you a listing of the processes and their pid' although with the update frequency set high, it is difficult to identify the correct pid as the lines of the displayed processes keep changing.
While top is running hit the "h" key which will bring up a list of configurable settings. The "d or s" key can be used to change the update frequency to something longer than 3 seconds making it easier to catch the pid of the process you kill. Hit the "k" key to be able to enter the pid and the kill level of the process you want to kill. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
whereas, I am sure there are 1000 reasons why it is not a good script, . . . the following script "kl" usually works :- ............................... "kl" ___ #!/bin/sh # # kill process/program # while true do kill -9 `ps aux | grep -i $1 | awk '{ print $2 }'` sleep 2 done .................................. frienfly greetings -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 24 March 2007 07:16, riccardo35@gmail.com wrote:
whereas, I am sure there are 1000 reasons why it is not a good script,
. . . the following script "kl" usually works :-
Do you actually use that script? The process IDs produced will include that of the grep command, which will be gone by the time the kill occurs and thus elicit a diagnostic. Because the pattern is not bounded, or otherwise contextualized, it may find unrelated processes whose name, arguments or other ps output fields contain the target string specified. Using kill -9 as the first recourse inn terminating a process is usually inappropriate, but sometimes necessary. As I've said before, the "pidof" program is specifically designed to return the process IDs of those processes running a specific command. That's what should be used for this purpose. The default SIGTERM (15) should be used first and only if that fails to stop the process should SIGKILL (9) be used. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 24 March 2007 09:16, riccardo35@gmail.com wrote:
whereas, I am sure there are 1000 reasons why it is not a good script, ... kill -9 ...
There is 1000 and first, not to use kill -9 as a regular procedure. All users that render their system useless because they used too often kill -9 will tell you that Linux is as bad as any other OS, as applications are not running (lock files are not removed), failing one by one (as user applies kill -9). What kill -9 does is to turn power switch off for the affected application. Many applications will refuse to start because they check only if there is their own lock file, and as previous run finished withoot giving program chance to remove lock file it will not run, like Firefox in first post of this thread. The signal 9 is mighty tool if used for what it is intended. To remove processes that doesn't respond to normal request to quit, but used everywhere it is more like using hammer to center picture on your monitor ;-) -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 24. March 2007 16:03:25 Rajko M. wrote:
On Saturday 24 March 2007 09:16, riccardo35@gmail.com wrote:
whereas, I am sure there are 1000 reasons why it is not a good script,
...
kill -9
...
There is 1000 and first, not to use kill -9 as a regular procedure.
All users that render their system useless because they used too often kill -9 will tell you that Linux is as bad as any other OS, as applications are not running (lock files are not removed), failing one by one (as user applies kill -9).
What kill -9 does is to turn power switch off for the affected application. Many applications will refuse to start because they check only if there is their own lock file, and as previous run finished withoot giving program chance to remove lock file it will not run, like Firefox in first post of this thread.
The signal 9 is mighty tool if used for what it is intended. To remove processes that doesn't respond to normal request to quit, but used everywhere it is more like using hammer to center picture on your monitor
In place of kill it is imo better to use pkill / pgrep. Especially if you are working with Solaris from time to time you will be glad not to use killall (as often mentioned the in linux doc's). Killall on Solaris does what it says, it kills _all_ processes. From man pkill: PGREP(1) Linux User’s Manual PGREP(1) NAME pgrep, pkill - look up or signal processes based on name and other attributes SYNOPSIS pgrep [-flvx] [-d delimiter] [-n|-o] [-P ppid,...] [-g pgrp,...] [-s sid,...] [-u euid,...] [-U uid,...] [-G gid,...] [-t term,...] [pattern] pkill [-signal] [-fvx] [-n|-o] [-P ppid,...] [-g pgrp,...] [-s sid,...] [-u euid,...] [-U uid,...] [-G gid,...] [-t term,...] [pattern] DESCRIPTION pgrep looks through the currently running processes and lists the process IDs which matches the selection criteria to std‐ out. All the criteria have to match. For example, $ pgrep -u root sshd will only list the processes called sshd AND owned by root. On the other hand, $ pgrep -u root,daemon will list the processes owned by root OR daemon. pkill will send the specified signal (by default SIGTERM) to each process instead of listing them on stdout. ... So if you are a novice Linux user don't start using kill or killall. Start using pkill / pgrep instead. regards, thomas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 24 March 2007, Hylton Conacher (ZR1HPC) wrote:
Donald D Henson wrote:
Hi Donald,
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
I think the command you are looking for is 'top' ie executed from an unprivleged user: $> top
This will give you a listing of the processes and their pid' although with the update frequency set high, it is difficult to identify the correct pid as the lines of the displayed processes keep changing.
Rather use one of the other post' recommendations.
Regards Hylton ===========
Donald, Another program that works very well is ksysguard. It's a very good gui for viewing the processes running and allows you to kill them easily. Just use ctrl-esc keys to activate it from your KDE interface. Also, if you guys love "top" a lot, take a look at "htop"! I don't know if SuSE has a rpm for this or not, but it would be worth someone building. Maybe Packman has it. It also runs from the command line but makes using top so much easier! Plus, you have the complete list of programs running at a glance with the ability to kill, etc. any, much like ksysguard. It's also mouse & cursor keys accessible. And Donald, You Tube & Flash seem to be a constant source of problems such as you experienced. Maybe Adobe will get it right one day or people will just quit using it. regards, Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 24 March 2007 11:23:13 pm BandiPat wrote:
On Saturday 24 March 2007, Hylton Conacher (ZR1HPC) wrote:
Donald D Henson wrote:
Hi Donald,
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
I think the command you are looking for is 'top' ie executed from an unprivleged user: $> top
This will give you a listing of the processes and their pid' although with the update frequency set high, it is difficult to identify the correct pid as the lines of the displayed processes keep changing.
Rather use one of the other post' recommendations.
Regards Hylton
===========
Donald, Another program that works very well is ksysguard. It's a very good gui for viewing the processes running and allows you to kill them easily. Just use ctrl-esc keys to activate it from your KDE interface.
Also, if you guys love "top" a lot, take a look at "htop"! I don't know if SuSE has a rpm for this or not, but it would be worth someone building. Maybe Packman has it. It also runs from the command line but makes using top so much easier! Plus, you have the complete list of programs running at a glance with the ability to kill, etc. any, much like ksysguard. It's also mouse & cursor keys accessible.
And Donald, You Tube & Flash seem to be a constant source of problems such as you experienced. Maybe Adobe will get it right one day or people will just quit using it.
You can get htop via smart. Fred -- If guns cause crime, then pencils cause misspelled words. If guns cause crime, then matches cause arson. "Those who hammer their guns into plows will plow for those who do not." Thomas Jefferson -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 24 March 2007 20:23, BandiPat wrote:
....
Also, if you guys love "top" a lot, take a look at "htop"! ...
That looks interesting, but I cannot seem to find one feature of top that I like to use, namely top's "n" command which allows you to limit the number of processes shown. Does htop have an equivalent I'm not seeing?
regards, Lee
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 25 March 2007, Randall R Schulz wrote:
On Saturday 24 March 2007 20:23, BandiPat wrote:
....
Also, if you guys love "top" a lot, take a look at "htop"! ...
That looks interesting, but I cannot seem to find one feature of top that I like to use, namely top's "n" command which allows you to limit the number of processes shown.
Does htop have an equivalent I'm not seeing?
regards, Lee
Randall Schulz ==============
Randall, I haven't dug deeply into the workings of htop yet, I was just very pleased not to have to deal with top anymore! I had used ksysguard when I ran KDE, but since using Xfce4 so much, I've come to appreciate the power of top, but with the simplicity of ksysguard. regards, Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2007-03-24 at 23:23 -0400, BandiPat wrote:
On Saturday 24 March 2007, Hylton Conacher (ZR1HPC) wrote:
Donald D Henson wrote:
Hi Donald,
I seem to have gotten myself into a situation where a Firefox process will not die nor will it display anything. (The problem seems to have something to do with You Tube.) When I try to start up another instance of Firefox, I get an error message that tells me to either close the current process or to reboot the system. Rebooting is not a good solution. I remember from the 'old days' that there is a cli command to identify a process id and another one to kill a process. I've searched my memory and the User Manual but cannot identify those two commands. Any assistance will be sincerely appreciated.
-snip- This thread branched off into talking about 'top', 'htop' and other utilities, but the original poster is best served (IMHO) by the two cli utilities from bash, namely 'ps' and 'kill'. In a terminal enter 'ps aux' to see a list of processes with pid (process ID) and user. Identify the pid you want and then enter 'kill yyyy' where 'y' is the pid number. You can do this as a user only if the pid belongs to you, but must be superuser to kill root and other user pids. Sometimes a pid won't die and you have to enter 'kill -9 xxxx'. Other times a zombie process won't die whatever you do, usually when hardware is involved, such as a dvd drive. Sadly, in that case you DO have to reboot, because even killing X won't affect the zombie. See 'man ps' and 'man kill'. Gavin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Gnome System Monitor also works great. On one machine I use Gnome a lot so It helps to have something handy on the tool bar. I keep it on the lower one. CWSIV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (18)
-
BandiPat -
Carl William Spitzer IV -
Donald D Henson -
email.listen＠googlemail.com -
Fred A. Miller -
Gavin Chester -
Hylton Conacher (ZR1HPC) -
Jay C Vollmer -
Jerry Feldman -
Jonathan Arnold -
Kenneth Schneider -
M Harris -
Matthias Titeux -
Philippe Andersson -
Rajko M. -
Randall R Schulz -
riccardo35＠gmail.com -
Robert Lewis