Hi,
How do you kill a process in SUSE 13.1 Linux step by step?
Thank you
You might be able to do it in the console by running this command:
top
Look for the process you want to kill, and type
k****
Replace the “****” with the pid of the process. Press “q” to quit after.
Run
ps -A
to list processes, determine the PID of the process to kill then
kill PID
will kill the PID process
GUI method depend on the GUI used
in KDE run ksysguard right click process to kill select end process or press del key to kill it
Note depending on the process owner you may need to be root to kill a given process
gamergoat89 wrote:
>
> Hi,
> How do you kill a process in SUSE 13.1 Linux step by step?
> Thank you
>
>
Console/terminal based approach
open a gnome terminal/konsole or whatever terminal emulator you use and
list all processes using the command
ps -A
Then you can issue a killall command after identifying name of you need
to terminate. Here i have used the application “parcellite”
killall parcellite
(OR)
GUI based approach
If you have desktop like GNOME you can open process monitors like
gnome-system-monitor and terminate processes using those applications
–
GNOME 3.10.2
openSUSE 13.1 (Bottle) (x86_64) 64-bit
Kernel Linux 3.11.6-4-desktop
Still doesn’t work.
The app is frozen.
Cant terminate it for some reason.
Which app and who owns it?
It does not work even if you are root??
If so it is a zombie. There are methods to deal with that but i has been a long tome since I had to deal with a zombie
try as root kill -9 PID
Zombies can be very hard to kill so sometime a reboot may be the only way to destroy them
gtkpod. I was trying to add music to my iPod.
yeah I think its a zombie because not even that command worked.
didnt work
You may have to shoot them in the head, it works in the movies lol! Sorry, I couldn’t resist!
HighBloodSugar wrote:
>
> gogalthorp;2629458 Wrote:
>>
>>
>> Zombies can be very hard to kill so sometime a reboot may be the only
>> way to destroy them
>
> You may have to shoot them in the head, it works in the movies lol!
> Sorry, I couldn’t resist!
>
>
No cutting their heads off is the only way to kill them 
–
GNOME 3.10.2
openSUSE 13.1 (Bottle) (x86_64) 64-bit
Kernel Linux 3.11.6-4-desktop
When you now think some people here are making a joke of it, that is at least partly your own fault. You give no informatioin at all. Show us that ps list and tell us which one it is. Then we can discuss further steps to gather more information and ty to help you with more severe kll parameters… We are not clairvoyant.
On 2014-03-09 12:36, hcvv wrote:
>
> gamergoat89;2629452 Wrote:
>> Still doesn’t work.
>> The app is frozen.
>> Cant terminate it for some reason.
> When you now think some people here are making a joke of it, that is at
> least partly your own fault. You give no informatioin at all. Show us
> that ps list and tell us which one it is. Then we can discuss further
> steps to gather more information and ty to help you with more severe kll
> parameters… We are not clairvoyant.
Right…
One possibility is that one is trying to kill the wrong process.
What I do is display the process tree, with “ps afx | less -S” in a
terminal, then locate the process in question. See if it has children or
parents.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Im new to SUSE I dont really know how to print screen and paste on paint like in windows.
I am sorry
I hope I didn’t offend the OP, that wasn’t my intention, just being silly.
On 2014-03-09 17:46, gamergoat89 wrote:
>
> robin_listas;2629514 Wrote:
>> What I do is display the process tree, with “ps afx | less -S” in a
>> terminal, then locate the process in question. See if it has children or
>> parents.
>
> Im new to SUSE I dont really know how to print screen and paste on paint
> like in windows.
> I am sorry
I’ll try.
I open a terminal, for instance, “xfce-terminal” or “xterm”. In it, I type:
ps afxu | less -S
I see a long list of text, and I can move up-down, left-right, with the
cursor keys.
Near the end, I see this text:
> cer 31561 0.2 0.1 67412 8392 ? S 19:17 0:00 xterm
> cer 31563 0.2 0.0 14644 3352 pts/38 Ss 19:17 0:00 \_ bash
> cer 31585 0.0 0.0 16460 1672 pts/38 R+ 19:17 0:00 \_ ps afxu
> cer 31586 0.0 0.0 6952 1044 pts/38 S+ 19:17 0:00 \_ less
which is precisely the command I typed, which has a parent and several
children. You can see the hierarchy.
The PID number of each process is the second column, with numbers.
Killing 31586 is possible, but the rest might remain running. Killing
31585 fails (No such process). Kill 31563 simply refuses. You can “kill
-9 31563” and then the entire terminal dies, even if I did not kill the
terminal. A normal kill of “31561”, the parent, kills them all.
Some processes are really dead, but show in the list. Zombies. Undead.
They are waiting for something else to die. IIRC. Might be wrong.
To copy that text here, what I did was simply select the text with the
mouse, exactly as I would do in Windows (maybe not, I forget how I do in
windows). Click on top, move mouse down, release.
Then go to the place you want to paste that text. Press and hold
“shift”, then left click. Text is pasted!
If you want to do an screenshot, on some desktops simply press the
printscreen key. Sometimes you have to install something first. On some
desktops this does not work. Ask then
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
In general zombies take up few resources but they do use up PID numbers of which there are a limited number. So as long as there are only a few zombies It is not a huge deal normally but if you have a bunch it may limit the number of processes you can start. In any case zombies are cleared by a reboot in all cases. If you have a bunch then some process is not properly shutdown its children.
On Sun, 09 Mar 2014 04:26:02 +0000, gogalthorp wrote:
> Zombies can be very hard to kill so sometime a reboot may be the only
> way to destroy them
Typically, the way you kill a zombie is by killing its parent process -
that’s /supposed/ to be the proper way to clean them up.
Of course, if they’re owned by PID 1, then yeah, a reboot is the only way
to fix it.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Sun, 09 Mar 2014 04:46:01 +0000, gamergoat89 wrote:
> gogalthorp;2629458 Wrote:
>> Which app and who owns it?
>>
>> It does not work even if you are root??
>>
>> If so it is a zombie. There are methods to deal with that but i has
>> been a long tome since I had to deal with a zombie
>>
>> try as root kill -9 PID
>>
>> Zombies can be very hard to kill so sometime a reboot may be the only
>> way to destroy them
>
> gtkpod. I was trying to add music to my iPod.
> yeah I think its a zombie because not even that command worked.
> didnt work
That’s not a guarantee that it’s a zombie. Do:
ps ax | grep gtkpod
In the 3rd column, what’s the letter?
If it’s not a Z, it’s not a zombie.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Sun, 09 Mar 2014 22:52:16 +0000, Jim Henderson wrote:
> On Sun, 09 Mar 2014 04:26:02 +0000, gogalthorp wrote:
>
>> Zombies can be very hard to kill so sometime a reboot may be the only
>> way to destroy them
>
> Typically, the way you kill a zombie is by killing its parent process -
> that’s /supposed/ to be the proper way to clean them up.
>
> Of course, if they’re owned by PID 1, then yeah, a reboot is the only
> way to fix it.
It’s also important to know, though, that a zombie process isn’t actually
a process. It takes up a little space in the process table, but there’s
no other memory allocation or executable code left in memory (from what I
recall). The only time they can become a real problem is if they respawn
and fill up the process table.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Sun, 09 Mar 2014 04:46:01 +0000, gamergoat89 wrote:
> gtkpod. I was trying to add music to my iPod.
A thought occurs - if it’s a process that’s hung during an I/O operation,
then it’s probably not a zombie, but waiting on the I/O channel to clear.
It might be beneficial rather than to ask “how do I kill a process” to
state what you’re doing and what the specific problem you’re having is -
we can troubleshoot that, and if killing the process is the right way to
deal with it, then someone can help you with that.
That’s probably a better approach than just starting with the “nuke it
till it glows” option. 
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C