04-13-2006
Let's say that the pid is 1612. So you set tcpid to 1612 and then you enter your loop. On the first iteration you kill the process. After the process dies, the value of $tcpid will not magically change values for you. It is still 1612. It will stay 1612 forever since you don't assign it a new value in the loop.
What is the point of the loop anyway? If a process survived a "kill -9", do you think that second "kill -9" will work any better?
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
can anyone send me enything about "unix process control "
nicko@freemail.com.mk (2 Replies)
Discussion started by: nicko
2 Replies
2. Programming
Hello,
I want to know what call to use to read the details of a process control block in solaris ?:) (2 Replies)
Discussion started by: hmurali
2 Replies
3. UNIX for Advanced & Expert Users
I found that in my system , there are some strange process , it will make the system crash so I would like to control the system no such process is running ,
this is if the system process that its process name is "ora" AND its ppid is not "2" , then it will crash the system, can suggest how to... (2 Replies)
Discussion started by: ust
2 Replies
4. UNIX for Dummies Questions & Answers
I'm trying to wrap my head around process control in Unix... particularly init and how it fits in to the equation. Init is responsible for creating sessions by spawning instances of getty which calls login effectively creating sessions right? Why then can init belong to a session? If you ps jx... (4 Replies)
Discussion started by: dexfantasy
4 Replies
5. Shell Programming and Scripting
Dear all,
I want to control my server from shutting down and rebooting.
It will ask for some question before the process, ex: who are you? what is the reason for shutting down? ...
I think I can overide that binary of shutdown/reboot command, but it is confused.
We have many way to... (5 Replies)
Discussion started by: fongthai
5 Replies
6. UNIX for Advanced & Expert Users
I pressed CTRL Z and suspended the job. then I pressed bg, The process re-started to throw output on the terminal and its not allowing me to access the prompt.
its not even accepting CTRL Z. The process has been running for about 2 hours now and I want to suspend it by opening another terminal.... (3 Replies)
Discussion started by: rakeshou
3 Replies
7. Shell Programming and Scripting
Hi forum,
I have a problem concerning job or process scheduling and control.
I have to run 24 jobs (could be more sometimes less) of the same programme with different parameters. The machine this code is running on is an 8-core machine, so I was thinking that running all the processes at once... (0 Replies)
Discussion started by: deiphon
0 Replies
8. Shell Programming and Scripting
Hi,
I'm using simple sqlplus to test DB availability.
When DB is going down, sqlplus command is hang for a few minutes
I want to implement the following:
1. execute sqlplus
2. if after 20 sec I dont get a response, kill the process and exit with error.
3. if I get immediate response... (2 Replies)
Discussion started by: gdan2000
2 Replies
9. Shell Programming and Scripting
Hi Friends,
Iam invoking another shell script to create B2k_session_id from my shell script.It is properly creating B2k_session_id and after creation control is coming out from the script and going to command prompt.The lines which are after the exectrusteduser.com sh.com are not executing..may... (5 Replies)
Discussion started by: vadlamudy
5 Replies
preap(1) User Commands preap(1)
NAME
preap - force a defunct process to be reaped by its parent
SYNOPSIS
preap [-F] pid...
DESCRIPTION
A defunct (or zombie) process is one whose exit status has yet to be reaped by its parent. The exit status is reaped via the wait(3C),
waitid(2), or waitpid(3C) system call. In the normal course of system operation, zombies may occur, but are typically short-lived. This may
happen if a parent exits without having reaped the exit status of some or all of its children. In that case, those children are reparented
to PID 1. See init(1M), which periodically reaps such processes.
An irresponsible parent process may not exit for a very long time and thus leave zombies on the system. Since the operating system destroys
nearly all components of a process before it becomes defunct, such defunct processes do not normally impact system operation. However, they
do consume a small amount of system memory.
preap forces the parent of the process specified by pid to waitid(3C) for pid, if pid represents a defunct process.
preap will attempt to prevent the administrator from unwisely reaping a child process which might soon be reaped by the parent, if:
o The process is a child of init(1M).
o The parent process is stopped and might wait on the child when it is again allowed to run.
o The process has been defunct for less than one minute.
OPTIONS
The following option is supported:
-F Forces the parent to reap the child, overriding safety checks.
OPERANDS
The following operand is supported:
pid Process ID list.
EXIT STATUS
The following exit values are returned by preap, which prints the exit status of each target process reaped:
0 Successfully operation.
non-zero Failure, such as no such process, permission denied, or invalid option.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWesu (32-bit) |
+-----------------------------+-----------------------------+
| |SUNWesxu (64-bit) |
+-----------------------------+-----------------------------+
SEE ALSO
proc(1), init(1M), waitid(2), wait(3C), waitpid(3C), proc(4), attributes(5)
WARNINGS
preap should be applied sparingly and only in situations in which the administrator or developer has confirmed that defunct processes will
not be reaped by the parent process. Otherwise, applying preap may damage the parent process in unpredictable ways.
SunOS 5.10 26 Mar 2001 preap(1)