04-15-2009
A true zombie process is already dead. Your Operating System should clean them up for you. If they persist then they are usually stuck on unfinished i/o and it takes a reboot to remove them from the process table.
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Okay, I'm working within ansi C and Sun Solaris 7. I have a problem with zombies. I'm currently using the kill command to return the status of a process. How do I check for Zombie PIDs or the right function to return its PID from within a C program? (1 Reply)
Discussion started by: karpolu
1 Replies
2. UNIX for Dummies Questions & Answers
Is there a command that will automaticaly go through and kill all children when you try to kill the parent process.
Thanks,
David (3 Replies)
Discussion started by: nucca
3 Replies
3. HP-UX
Hi All
I need help, how can i kill zombies instead of rebooting the system.
Regards
System: sna Tue Apr 5 17:50:23 2005
Load averages: 0.05, 0.15, 0.22
168 processes: 157 sleeping, 5 running, 6 zombies
Cpu states:
CPU LOAD USER NICE... (5 Replies)
Discussion started by: cgege
5 Replies
4. Programming
i'm writing small http proxy server (accept client -> connect to remote proxy server -> recv client's request -> send to remote proxy server -> get responce from remote proxy server -> send answer to client -> close connection to client and to remote proxy server) and having problems with fork().... (2 Replies)
Discussion started by: PsycoMan
2 Replies
5. Programming
what are the precautions to be taken care for avoiding zombie process ? (8 Replies)
Discussion started by: Gopi Krishna P
8 Replies
6. UNIX for Dummies Questions & Answers
Hello, quick question:
I have a zombie process listed with 'top'
Could someone help me find out what it the PID is for it,
so I can kill $PID.
$ model
9000/800/rp3440
HP-UX bigassserver B.11.31 U 9000/800 3085785128 unlimited-user license
thanks!
System: bigassserver ... (23 Replies)
Discussion started by: olyanderson
23 Replies
LEARN ABOUT SUSE
runit-init
runit-init(8) System Manager's Manual runit-init(8)
NAME
init - a UNIX process no 1
SYNOPSIS
init [ 0 | 6 ]
DESCRIPTION
runit-init is the first process the kernel starts. If runit-init is started as process no 1, it runs and replaces itself with runit(8).
If runit-init is started while the system is up, it must be either called as init 0 or init 6:
init 0 tells the Unix process no 1 to shutdown and halt the system. To signal runit(8) the system halt request, runit-init removes all
permissions of the file /etc/runit/reboot (chmod 0), and sets the execute by owner permission of the file /etc/runit/stopit (chmod
100). Then a CONT signal is sent to runit(8).
init 6 tells the Unix process no 1 to shutdown and reboot the system. To signal runit(8) the system reboot request, runit-init sets the
execute by owner permission of the files /etc/runit/reboot and /etc/runit/stopit (chmod 100). Then a CONT signal is sent to
runit(8).
EXIT CODES
runit-init returns 111 on error, 0 in all other cases.
SEE ALSO
runit(8), runsvdir(8), runsvchdir(8), sv(8), runsv(8), chpst(8), utmpset(8), svlogd(8)
http://smarden.org/runit/
AUTHOR
Gerrit Pape <pape@smarden.org>
runit-init(8)