Sponsored Content
Full Discussion: processes
Top Forums UNIX for Advanced & Expert Users processes Post 6051 by rajusom on Wednesday 29th of August 2001 03:49:38 AM
Old 08-29-2001
Thanx a lot but still i have one doubt, if i dont know how the parent process of the Zombie processes , than how can i track the parent process and since the zombie processes are attached to root than only root can kill it. is there any solution that i should restrict zombie process up to some extent at the user level.

Last edited by rajusom; 08-29-2001 at 04:55 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

co-processes

Is it possible to have a main script (i will call it main.ksh) that executes say, 4 other scripts (sub_prog_1.ksh, sub_prog_2.ksh etc..) from within this main.ksh (simultaneously/in parallel), have them run in the background and communicate back to main.ksh when complete? My guess is to use... (1 Reply)
Discussion started by: google
1 Replies

2. UNIX for Dummies Questions & Answers

processes

What command string will locate ONLY the PID of a process and ouput only the number of PID of the process? (1 Reply)
Discussion started by: mma_buc_98
1 Replies

3. Shell Programming and Scripting

I need some example of Co-Processes

I want to know how to work the Co-Processes in kornshell scripts. So, I very need some script about Co-Processes! thanks ...:) (3 Replies)
Discussion started by: javalee
3 Replies

4. Filesystems, Disks and Memory

processes

write a program create two processes to run a for loop which adds numbers 1 to n , say one process adds odd numbers and other adds even numbers (1 Reply)
Discussion started by: jayaram_miryabb
1 Replies

5. Shell Programming and Scripting

Processes

I have a file like this. No. State Query Times User Processed Syslog 1 ready idle 973s 0 /Application/ugsvols/bldata01/logs/imanscript1562.syslog 2 ready idle 803s 83997 13 /Application/ugsvols/bldata01/logs/imanscript1542.syslog 3 ready idle 2954s 106641... (17 Replies)
Discussion started by: Krrishv
17 Replies

6. UNIX for Advanced & Expert Users

Monitoring Processes - Killing hung processes

Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go? Thank you Richard (4 Replies)
Discussion started by: ukndoit
4 Replies

7. Solaris

Identifying and grouping OS processes and APP processes

Hi Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages. Any free tools or scripts to do this? Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies

8. UNIX for Dummies Questions & Answers

Processes

Hi all, I needed a little help. It's OS thing. Suppose I have 2 machine connect over a network, I will call my machines as M1and M2. If I copy a files from M1 to M2. What tasks are these two machine performing for copy to work. My assumption is that M1 is performing read action and... (1 Reply)
Discussion started by: vishwesh
1 Replies

9. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies

10. UNIX for Dummies Questions & Answers

processes

may i know a command to find processes not attached to a terminal?? (1 Reply)
Discussion started by: riya9
1 Replies
wait(3) 						     Library Functions Manual							   wait(3)

NAME
wait - check child process status SYNTAX
#include <wait.h> int wait_nohang(&wstat); int wait_stop(&wstat); int wait_stopnohang(&wstat); int wait_pid(&wstat,pid); int wait_exitcode(wstat); int wait_crashed(wstat); int wait_stopped(wstat); int wait_stopsig(wstat); int pid; int wstat; DESCRIPTION
wait_nohang looks for zombies (child processes that have exited). If it sees a zombie, it eliminates the zombie, puts the zombie's exit status into wstat, and returns the zombie's process ID. If there are several zombies, wait_nohang picks one. If there are children but no zombies, wait_nohang returns 0. If there are no children, wait_nohang returns -1, setting errno appropriately. wait_stopnohang is similar to wait_nohang, but it also looks for children that have stopped. wait_stop is similar to wait_stopnohang, but if there are children it will pause waiting for one of them to stop or exit. wait_pid waits for child process pid to exit. It eliminates any zombie that shows up in the meantime, discarding the exit status. wait_stop and wait_pid retry upon error_intr. STATUS PARSING
If the child stopped, wait_stopped is nonzero; wait_stopsig is the signal that caused the child to stop. If the child exited by crashing, wait_stopped is zero; wait_crashed is nonzero. If the child exited normally, wait_stopped is zero; wait_crashed is zero; and wait_exitcode is the child's exit code. SEE ALSO
wait(2), error(3) wait(3)
All times are GMT -4. The time now is 11:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy