View previous topic :: View next topic |
Author |
Message |
aleks04 n00b
Joined: 11 Feb 2003 Posts: 13
|
Posted: Thu Oct 21, 2004 2:59 pm Post subject: Another way to kill a process? |
|
|
I have been updating the system and left it running over night. Next day I see it stuck on merging samba. So I ^C the current process and everything seems fine. But for some reason there still is a [sh] process that is still running from that emerge and is taking up 99.9% of the CPU.
I have tried to `kill -9` the process but it's still running...
Code: |
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
1 0 12113 1 21 0 0 0 - R ? 1072:57 [sh]
|
Is there another way to try and kill off this process? |
|
Back to top |
|
|
hds Advocate
Joined: 21 Aug 2004 Posts: 2629 Location: Sprockhoevel [GER]
|
Posted: Thu Oct 21, 2004 3:24 pm Post subject: |
|
|
this is probably a child process of something else, so you cant kill it that way.
try "ps ax | grep sh" and see what gives. you would have to kill the "mother" of the sh process. |
|
Back to top |
|
|
DaveArb Guru
Joined: 29 Apr 2004 Posts: 510 Location: Texas, USA
|
Posted: Thu Oct 21, 2004 3:27 pm Post subject: |
|
|
hds wrote: | this is probably a child process of something else, so you cant kill it that way. |
It is a child process of init, the PPID in the listing is 1. Killing init is a Bad Idea.
Unfortunately, I have no good ideas to contribute. `kill -9 12113` should get it, or if it's a zombie init should reap it. Too many "shoulds" in the preceding sentence.
Dave |
|
Back to top |
|
|
aleks04 n00b
Joined: 11 Feb 2003 Posts: 13
|
Posted: Thu Oct 21, 2004 3:30 pm Post subject: |
|
|
Kill -9 doesn't work no matter what I do, and this process is using 99.9% of the CPU so it's running and it's not a zombie process... |
|
Back to top |
|
|
hds Advocate
Joined: 21 Aug 2004 Posts: 2629 Location: Sprockhoevel [GER]
|
Posted: Thu Oct 21, 2004 3:31 pm Post subject: |
|
|
DaveArb wrote: |
It is a child process of init, the PPID in the listing is 1. |
duh! you are right, didnt look close enough.
well, he "could" try "killall sh" - without any warranty.
OTOH - i'd simply reboot the sucker |
|
Back to top |
|
|
Monkeywrench Apprentice
Joined: 22 Jun 2004 Posts: 205 Location: Florida
|
Posted: Thu Oct 21, 2004 3:42 pm Post subject: |
|
|
Doesn't seem to be a zombie at all. Here's the Process State Codes from the ps man page:
Code: | PROCESS STATE CODES
Here are the different values that the s, stat and state output specifiers
(header "STAT" or "S") will display to describe the state of a process.
D Uninterruptible sleep (usually IO)
R Running or runnable (on run queue)
S Interruptible sleep (waiting for an event to complete)
T Stopped, either by a job control signal or because it is being traced.
W paging (not valid since the 2.6.xx kernel)
X dead (should never be seen)
Z Defunct ("zombie") process, terminated but not reaped by its parent. |
sh has state code R, which is supposed to be a normal running process.. Oh well... _________________ Folding@home -Join the Linux team (163)! |
|
Back to top |
|
|
DaveArb Guru
Joined: 29 Apr 2004 Posts: 510 Location: Texas, USA
|
Posted: Thu Oct 21, 2004 6:03 pm Post subject: |
|
|
hds wrote: | OTOH - i'd simply reboot the sucker |
Yeah, me too.
Dave |
|
Back to top |
|
|
aleks04 n00b
Joined: 11 Feb 2003 Posts: 13
|
Posted: Thu Oct 21, 2004 6:22 pm Post subject: |
|
|
Don't want to reboot it... atleast just yet... if I don't find a solution then I guess I will have to.
Did a little research on the subject and other things and found this:
The process is executing in the kernel mode and is running, but in kernel mode no signals get to the process so ofcourse it can't receive the TERM or STOP or any other signal.
Also I see that the process was using some files:
Code: |
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
sh 12113 root cwd DIR 3,6 0 1203508 /var/tmp/portage/samba-3.0.7-r1/work/samba-3.0.7/source (deleted)
sh 12113 root rtd DIR 3,5 4096 2 /
sh 12113 root 0u CHR 136,2 1450 /dev/pts/2 (deleted)
sh 12113 root 1u CHR 136,2 1450 /dev/pts/2 (deleted)
sh 12113 root 2u CHR 136,2 1450 /dev/pts/2 (deleted)
sh 12113 root 4r REG 3,6 1778 97541 /var/cache/edb/mtimedb (deleted)
|
Is there any way to kill a process executing in kernel mode? |
|
Back to top |
|
|
codeslave n00b
Joined: 19 Jan 2004 Posts: 5 Location: Boston, MA
|
Posted: Thu Oct 21, 2004 7:42 pm Post subject: |
|
|
I had a similar issue trying to kill a java process in HPUX, about 2 weeks ago. The process was hung, but not a zombie, and top was listing it at 100% CPU usage (though it didnt seem to be consuming any CPU in actuality). Kill -9 with superuser did nothing, etc. etc.
After much digging, we think we figured out what happened: The process was stuck waiting for an I/O operation to complete, but that had died unexpectedly, so our process was indefinitely waiting for something that would never come.
Sending the kill was never seen by the process, since the I/O operation must complete before continuing execution.
The only way we could get the process to die was to shutdown -r the machine.
/cs |
|
Back to top |
|
|
madmango Guru
Joined: 15 Jul 2003 Posts: 507 Location: PA, USA
|
Posted: Thu Oct 21, 2004 8:00 pm Post subject: |
|
|
I get this stuff ALL THE TIME when I'm dealing with usb drives. It sucks.
Is it the intention of the kernel people for a process to not be able to die during an IO operation? _________________ word. |
|
Back to top |
|
|
Yann|ck n00b
Joined: 28 May 2003 Posts: 4
|
Posted: Tue May 24, 2005 12:59 pm Post subject: |
|
|
I'm also having this problem on a mail server box.
top shows:
Code: | [...]
Cpu0 : 88.9% us, 10.4% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.7% hi, 0.0% si
Cpu1 : 0.0% us, 100.0% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
Cpu2 : 94.8% us, 4.4% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.7% si
Cpu3 : 94.8% us, 5.2% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
[...]
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ PPID SWAP nFLT nDRT WCHAN COMMAND
24680 qscand 17 0 0 0 0 R 99.8 0.0 239:15.12 1 0 0 0 - qmail-scanner-q
|
That process is monopolizing the Cpu1 (100% system).
No way to get rid of it. I tried all the kill signals.
If anyone has an idea on how to kill that kind of process - or on how to avoid them, (s)he's welcome!
Yannick |
|
Back to top |
|
|
nbensa l33t
Joined: 10 Jul 2002 Posts: 799 Location: Buenos Aires, Argentina
|
Posted: Fri Aug 19, 2005 6:42 am Post subject: |
|
|
/me badly wants a kernel patch to kill D state process |
|
Back to top |
|
|
sfroe n00b
Joined: 22 Jul 2005 Posts: 18
|
Posted: Fri Aug 19, 2005 7:55 pm Post subject: |
|
|
how about a good ol kill -15 ???
it might just work. that way it can try to stop the IO operation instead of killing the process and the IO operation taking over and stopping the -9. |
|
Back to top |
|
|
zeek Guru
Joined: 16 Nov 2002 Posts: 480 Location: Bantayan Island
|
Posted: Sat Aug 20, 2005 7:25 am Post subject: |
|
|
In situations like this, take a minute to remember all the linux nuthuggers and fanbois droning on and on about the stability of linux and the instability of windows. It goes to show that even linux has its problems sometimes.
Reboot to get rid of the process(es). |
|
Back to top |
|
|
AdShea n00b
Joined: 10 Mar 2005 Posts: 62
|
Posted: Thu Nov 10, 2005 7:06 pm Post subject: |
|
|
I had a bunch of nasty sh processes, logging out the user who started them helped for me. But if they're root processes, that may not work so well.- |
|
Back to top |
|
|
sundialsvc4 Guru
Joined: 10 Nov 2005 Posts: 436
|
Posted: Fri Nov 11, 2005 1:20 am Post subject: |
|
|
zeek wrote: | In situations like this, take a minute to remember all the linux nuthuggers and fanbois droning on and on about the stability of linux and the instability of windows. It goes to show that even linux has its problems sometimes.
Reboot to get rid of the process(es). | Of course it does.
The fact that PPID=1 probably means that it's "died and gone to heaven," or that its original owner has otherwise died. init may have wound up with it, but init didn't spawn it, to be sure...
This reminds me of what can happen if a process is waiting for a mandatory file-lock or something like it. What puzzles me is why that would be "100% CPU busy," and I wonder if that number is really accurate or not. Anything in /proc/pid/status? Is that CPU accepting any other work?
I'm sure a reboot will be required to clear the condition, but it's valid to study it a little while to try to find out why. I agree that these problems are often "somehow device-related," and the idea that it might be related to a removable device is a good one to pursue. |
|
Back to top |
|
|
tnt Veteran
Joined: 27 Feb 2004 Posts: 1227
|
Posted: Sun Jan 29, 2006 5:46 am Post subject: |
|
|
I'm getting more and more "defunct" processes.
Code: | ps axu
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 1464 76 ? S 2005 0:00 init [3]
root 2 0.0 0.0 0 0 ? SN 2005 0:01 [ksoftirqd/0]
root 3 0.0 0.0 0 0 ? S< 2005 0:00 [events/0]
root 4 0.0 0.0 0 0 ? S< 2005 0:00 [khelper]
root 5 0.0 0.0 0 0 ? S< 2005 0:00 [kthread]
root 7 0.0 0.0 0 0 ? S< 2005 0:00 [kacpid]
root 117 0.0 0.0 0 0 ? S< 2005 0:03 [kblockd/0]
root 120 0.0 0.0 0 0 ? S 2005 0:00 [khubd]
root 161 0.0 0.0 0 0 ? S< 2005 0:00 [aio/0]
root 160 0.0 0.0 0 0 ? S 2005 1:16 [kswapd0]
root 751 0.0 0.0 0 0 ? S 2005 0:00 [kseriod]
root 820 0.0 0.0 0 0 ? S 2005 0:00 [md1_raid1]
root 821 0.0 0.0 0 0 ? S 2005 0:00 [md0_raid1]
root 822 0.0 0.0 0 0 ? S< 2005 0:01 [reiserfs/0]
root 870 0.0 0.0 0 0 ? Z<s 2005 0:00 [udevd] <defunct>
root 6036 0.0 0.0 0 0 ? S 2005 0:00 [khpsbpkt]
root 6058 0.0 0.0 0 0 ? S 2005 0:00 [knodemgrd_0]
root 7603 0.0 0.0 1716 496 ? Ss 2005 0:18 /usr/sbin/syslog-ng
named 8053 0.0 0.0 0 0 ? Zs 2005 1:07 [named] <defunct>
root 8227 0.0 0.0 3388 292 ? Ss 2005 0:00 /usr/sbin/sshd
root 8267 0.0 0.0 0 0 ? Zs 2005 0:00 [apache2] <defunct>
root 8314 0.0 0.0 3356 156 ? Ss 2005 0:00 apcmain
at 8350 0.0 0.0 1784 200 ? Ss 2005 0:00 /usr/sbin/atd
root 8390 0.0 0.0 3384 180 ? S 2005 0:00 apcnis
root 8391 0.0 0.0 3356 292 ? S 2005 2:04 apcdev
root 8392 0.0 0.5 6384 2620 ? S 2005 1:22 ddclient - sleeping for 60 seconds
rpc 8847 0.0 0.0 1704 68 ? Ss 2005 0:00 /sbin/portmap
root 8889 0.0 0.0 0 0 ? Zs 2005 0:00 [smbd] <defunct>
root 8891 0.0 0.0 0 0 ? Zs 2005 0:26 [nmbd] <defunct>
root 8901 0.0 0.0 0 0 ? Z 2005 0:00 [smbd] <defunct>
root 8939 0.0 0.0 0 0 ? Zs 2005 0:00 [squid] <defunct>
root 9007 0.0 0.0 1724 176 ? Ss 2005 0:11 /usr/sbin/cron
root 9069 0.0 0.0 1500 80 tty1 Ss+ 2005 0:00 /sbin/agetty 38400 tty1 linux
root 9070 0.0 0.0 1500 80 tty2 Ss+ 2005 0:00 /sbin/agetty 38400 tty2 linux
root 9071 0.0 0.0 1504 80 tty3 Ss+ 2005 0:00 /sbin/agetty 38400 tty3 linux
root 9072 0.0 0.0 1504 80 tty4 Ss+ 2005 0:00 /sbin/agetty 38400 tty4 linux
root 9073 0.0 0.0 1500 80 tty5 Ss+ 2005 0:00 /sbin/agetty 38400 tty5 linux
root 9074 0.0 0.0 1500 80 tty6 Ss+ 2005 0:00 /sbin/agetty 38400 tty6 linux
root 27663 0.0 0.0 0 0 ? S 2005 0:28 [pdflush]
root 31737 0.0 0.1 8728 792 ? Ss 2005 0:00 /usr/bin/perl /usr/libexec/webmin/miniserv.pl /etc/webmin/miniserv.conf
root 5850 0.0 0.0 0 0 ? Zs 2005 0:01 [screen] <defunct>
root 5851 0.0 0.0 0 0 ? ZNs 2005 0:04 [emerge] <defunct>
root 637 0.0 0.0 0 0 ? Z 2005 0:00 [init] <defunct>
root 18350 0.0 0.0 0 0 ? Z 2005 0:01 [smbd] <defunct>
root 25040 0.0 0.0 0 0 ? Z 2005 0:00 [smbd] <defunct>
root 348 0.0 0.0 0 0 ? Z 2005 0:01 [smbd] <defunct>
root 3390 0.0 0.0 0 0 ? Z 2005 0:00 [smbd] <defunct>
root 6850 0.0 0.0 0 0 ? Zs 2005 0:00 [bash] <defunct>
root 6858 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 6859 0.0 0.0 0 0 ? ZNs 2005 0:02 [emerge] <defunct>
root 25639 0.0 0.0 0 0 ? ZN 2005 0:00 [conftest] <defunct>
root 24004 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 24005 0.0 0.0 0 0 ? Zs 2005 0:00 [revdep-rebuild] <defunct>
root 24402 0.0 0.0 0 0 ? Zs 2005 0:00 [smbd] <defunct>
root 24404 0.0 0.0 0 0 ? Z 2005 0:00 [smbd] <defunct>
root 24405 0.0 0.0 0 0 ? Zs 2005 0:00 [nmbd] <defunct>
root 24429 0.0 0.0 0 0 ? Z 2005 0:00 [smbd] <defunct>
root 6398 0.0 0.0 0 0 ? ZN 2005 0:00 [conftest] <defunct>
root 16041 0.0 0.0 0 0 ? Z 2005 0:00 [smbd] <defunct>
root 19443 0.0 0.0 6856 316 ? Ss 2005 0:00 /usr/sbin/smbd -D
root 19444 0.0 0.0 6856 84 ? S 2005 0:00 /usr/sbin/smbd -D
root 19446 0.0 0.1 3532 528 ? Ss 2005 0:40 /usr/sbin/nmbd -D
root 18513 0.0 0.0 0 0 ? Zs 2005 0:01 [screen] <defunct>
root 18514 0.0 0.0 0 0 ? ZNs 2005 0:04 [emerge] <defunct>
root 23434 0.0 0.0 0 0 ? Zs 2005 0:00 [bash] <defunct>
root 23517 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23518 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23651 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23652 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23747 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23748 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23750 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23751 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23753 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23754 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23757 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23758 0.0 0.0 0 0 ? Zs 2005 0:00 [sh] <defunct>
named 23845 0.0 0.0 0 0 ? Zs 2005 0:00 [named] <defunct>
root 24311 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 24312 0.0 0.0 0 0 ? Zs 2005 0:00 [sh] <defunct>
named 11521 0.0 0.3 5244 1804 ? Ss 2005 1:39 /usr/sbin/named -u named -n 1
root 11547 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 11548 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 11558 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 11559 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 23115 0.0 0.0 0 0 ? Z 2005 0:00 [ldd] <defunct>
root 23116 0.0 0.0 0 0 ? Z 2005 0:00 [grep] <defunct>
root 23117 0.0 0.0 0 0 ? Z 2005 0:00 [revdep-rebuild] <defunct>
root 23118 0.0 0.0 0 0 ? Z 2005 0:00 [ldd] <defunct>
root 23122 0.0 0.0 0 0 ? Zs 2005 0:00 [bash] <defunct>
root 5762 0.0 0.0 0 0 ? Zs 2005 0:01 [screen] <defunct>
root 5763 0.0 0.0 0 0 ? ZNs 2005 0:16 [emerge] <defunct>
root 11884 0.0 0.0 0 0 ? ZN 2005 0:00 [try] <defunct>
root 16023 0.0 0.0 0 0 ? ZN 2005 0:00 [sh] <defunct>
root 15710 0.0 0.0 0 0 ? Zs 2005 0:00 [bash] <defunct>
root 25607 0.0 0.0 0 0 ? Zs 2005 0:00 [bash] <defunct>
root 25817 0.0 0.0 0 0 ? Zs 2005 0:01 [screen] <defunct>
root 25818 0.0 0.0 0 0 ? ZNs 2005 0:17 [emerge] <defunct>
root 20146 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 20147 0.0 0.0 0 0 ? ZNs 2005 0:01 [emerge] <defunct>
root 26957 0.0 0.0 0 0 ? Zs 2005 0:00 [screen] <defunct>
root 26958 0.0 0.0 0 0 ? ZNs 2005 0:05 [emerge] <defunct>
root 11480 0.0 0.0 0 0 ? ZN 2005 0:00 [conftest] <defunct>
root 5153 0.0 0.0 0 0 ? Z 2005 0:00 [wall] <defunct>
root 5156 0.0 0.0 0 0 ? Z 2005 0:00 [wall] <defunct>
root 24681 0.0 0.0 0 0 ? Zs Jan07 0:00 [screen] <defunct>
root 24682 0.0 0.0 0 0 ? ZNs Jan07 0:02 [emerge] <defunct>
root 4070 0.0 0.0 0 0 ? Zs Jan07 0:00 [squid] <defunct>
root 4314 0.0 0.0 5148 236 ? Ss Jan07 0:00 /usr/sbin/squid -DYC
squid 4317 0.0 1.5 146032 8196 ? Sl Jan07 0:18 (squid) -DYC
root 4396 0.0 0.0 0 0 ? Zs Jan07 0:00 [screen] <defunct>
root 4397 0.0 0.0 0 0 ? ZNs Jan07 0:09 [emerge] <defunct>
root 18738 0.0 0.0 0 0 ? Z Jan08 0:00 [wall] <defunct>
root 18747 0.0 0.0 0 0 ? Z Jan08 0:00 [wall] <defunct>
tnt 31871 0.0 0.0 0 0 ? Zs Jan15 0:00 [bash] <defunct>
root 31877 0.0 0.0 0 0 ? Z Jan15 0:00 [su] <defunct>
root 1069 0.0 0.0 0 0 ? Zs Jan15 0:01 [screen] <defunct>
root 1070 0.0 0.0 0 0 ? ZNs Jan15 0:20 [emerge] <defunct>
root 3965 0.0 0.0 0 0 ? ZN Jan15 0:00 [try] <defunct>
root 11231 0.0 0.0 0 0 ? ZN Jan15 0:00 [try] <defunct>
root 15393 0.0 0.0 0 0 ? ZN Jan15 0:00 [sh] <defunct>
root 29949 0.0 0.0 0 0 ? ZN Jan15 0:00 [mysql_config] <defunct>
tnt 6911 0.0 0.0 0 0 ? Zs Jan15 0:00 [bash] <defunct>
root 6916 0.0 0.0 0 0 ? Z Jan15 0:00 [su] <defunct>
tnt 20181 0.0 0.0 0 0 ? Zs Jan18 0:00 [bash] <defunct>
root 20186 0.0 0.0 0 0 ? Z Jan18 0:00 [su] <defunct>
root 27628 0.0 0.0 0 0 ? Zs Jan18 0:00 [apache2] <defunct>
root 27855 0.0 0.0 0 0 ? Zs Jan18 0:00 [bash] <defunct>
root 27928 0.0 0.0 0 0 ? Zs Jan18 0:00 [apache2] <defunct>
root 9087 0.0 0.0 0 0 ? Zs Jan20 0:00 [screen] <defunct>
root 9088 0.0 0.0 0 0 ? ZNs Jan20 0:12 [emerge] <defunct>
root 19776 0.0 0.0 0 0 ? Z<s Jan20 0:00 [udevd] <defunct>
root 3759 0.0 0.0 0 0 ? ZN Jan20 0:00 [conftest] <defunct>
root 7101 0.0 0.0 0 0 ? Zs Jan20 0:00 [bash] <defunct>
root 20588 0.0 0.0 0 0 ? Zs Jan20 0:00 [bash] <defunct>
root 20775 0.0 0.3 3916 1928 ? Ss Jan20 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
root 20999 0.0 0.0 0 0 ? Zs Jan20 0:00 [screen] <defunct>
root 21000 0.0 0.0 0 0 ? ZNs Jan20 0:02 [emerge] <defunct>
root 21404 0.0 0.0 0 0 ? Zs Jan23 0:00 [screen] <defunct>
root 21405 0.0 0.0 0 0 ? ZNs Jan23 0:06 [emerge] <defunct>
root 5449 0.0 0.1 1696 540 ? S<s Jan23 0:00 /sbin/udevd --daemon
root 24930 0.0 0.0 0 0 ? Zs Jan23 0:00 [screen] <defunct>
root 24931 0.0 0.0 0 0 ? ZNs Jan23 0:12 [emerge] <defunct>
root 25840 0.0 0.0 0 0 ? S Jan23 0:03 [pdflush]
root 31235 0.0 0.0 0 0 ? Zs Jan25 0:00 [screen] <defunct>
root 31236 0.0 0.0 0 0 ? ZNs Jan25 0:04 [emerge] <defunct>
root 17625 0.0 0.0 0 0 ? Z Jan26 0:00 [wall] <defunct>
root 17634 0.0 0.0 0 0 ? Z Jan26 0:00 [wall] <defunct>
root 8236 0.0 0.0 0 0 ? Zs Jan27 0:00 [bash] <defunct>
root 8449 0.0 0.0 0 0 ? Zs Jan27 0:00 [bash] <defunct>
root 8540 0.0 0.0 0 0 ? Zs Jan27 0:00 [bash] <defunct>
root 8958 0.0 0.0 0 0 ? Zs Jan27 0:00 [bash] <defunct>
root 16229 0.0 0.0 0 0 ? Zs Jan27 0:00 [screen] <defunct>
root 16230 0.0 0.0 0 0 ? ZNs Jan27 0:12 [emerge] <defunct>
apache 24627 0.0 0.3 3916 1948 ? S 03:10 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 24631 0.0 0.4 4048 2112 ? S 03:10 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1537 0.0 0.4 4048 2116 ? S 06:52 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1538 0.0 0.4 4048 2116 ? S 06:52 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1541 0.0 0.4 4048 2108 ? S 06:52 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1544 0.0 0.4 4048 2120 ? S 06:52 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1550 0.0 0.4 4048 2108 ? S 06:53 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1552 0.0 0.4 4048 2108 ? S 06:54 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1757 0.0 0.4 4048 2088 ? S 06:55 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1770 0.0 0.3 3916 1968 ? S 06:56 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
apache 1771 0.0 0.3 3916 1968 ? S 06:56 0:00 /usr/sbin/apache2 -D DEFAULT_VHOST -d /usr/lib/apache2 -f /etc/apache2/ht
|
Is there any way to stop them multiplying?
I understand that I can't get rid of existing zobies, but how to stop new ones appear?
_________________ gentoo user |
|
Back to top |
|
|
|