09-02-2005
Unkillable processes are usually trying to complete a system call. The process will die once the system call completes. If you use glance you can see what the process is waiting for. If the process is inappropriately unkillable, the culprit is usually a defective driver.
10 More Discussions You Might Find Interesting
1. HP-UX
We are runing HPUX on a 7400 server.
Some of our users are sitting in records for hours at a time and locking essential records or tables (A discipline issue I know, and I'm working on it.... However).
Does anybody know of a way to automatically terminate processes that have been idle for a... (1 Reply)
Discussion started by: Yantoch
1 Replies
2. Shell Programming and Scripting
i have a very short file that has in it a line for a find command.
now, when i run this script and I kill the script later, using the ps -ef | grep scriptname. i noticed kill -9 kills the script itself but does not kill the internal find command that it gave birth to.
say theres a file... (0 Replies)
Discussion started by: Terrible
0 Replies
3. Shell Programming and Scripting
Hi guys,
I am new to Unix shell scripting. Can anyone of you tell me how to kill all the processes at a time for a particular user?(No listing the process ID of each process in the kill -9 command).
Thanks in Advance,
-Hary (5 Replies)
Discussion started by: tadi18
5 Replies
4. Solaris
mqm 17700 16815 0 0:00 <defunct>
kill -9 does not work, even as root (10 Replies)
Discussion started by: csaunders
10 Replies
5. Solaris
how to kill the processes of aperticular user?
because i have nearly 25000 process are there for perticular user. i need to kill.
Please provide the information?
Regards,
Rajesh (3 Replies)
Discussion started by: pmrajesh21
3 Replies
6. HP-UX
Hi,
I read a set of processes with:
ps -eaf|grep oracleTRLV
The result is:
oracle 23253 1 0 15:14:11 ? 0:00 oracleTRLV (LOCAL=NO)
oracle 23301 1 0 15:15:07 ? 0:00 oracleTRLV (LOCAL=NO)
oracle 22914 1 0 15:11:19 ? 0:00 oracleTRLV (LOCAL=NO)
How to I kill the "oracleTRLV" ones? Is there... (17 Replies)
Discussion started by: NicoMan
17 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am writing korn shell script. My requirement is, i have to kill the parent process and all of its child processes. Can some one please help me on this?
Thanks in advance for your help.. (1 Reply)
Discussion started by: Sheethal
1 Replies
8. Shell Programming and Scripting
for i in 'ps -f | grep textedit'
do
kill $i
done
I wrote this but it wont work.
I am trying to find processes and kill them.
Any help would be welcome. (1 Reply)
Discussion started by: hawaiifiver
1 Replies
9. Shell Programming and Scripting
Hi there, i've been searching all over and i thought i had understood the way i should go to kill all the processes related to a user. But i'm getting more confused then i was.
By lunch time i have to make a database backup, and for that all the users shoul logout. The problem is that many users... (4 Replies)
Discussion started by: vascobrito
4 Replies
10. Shell Programming and Scripting
Want to kill multiple processes by name. for the example below, I want to kill all 'proxy-stagerd_copy' processes.
I tried this but didn't work:
>> ps -ef|grep proxy_copy
root 991 986 0 14:45:34 ? 0:04 proxy-stagerd
root 1003 991 0 14:45:49 ? 0:01... (2 Replies)
Discussion started by: catalinawinemxr
2 Replies
wait(1) General Commands Manual wait(1)
NAME
wait - await process completion
SYNOPSIS
[pid]
DESCRIPTION
If no argument is specified, waits until all processes (started with of the current shell have completed, and reports on abnormal termina-
tions. If a numeric argument pid is given and is the process ID of a background process, waits until that process has completed. Other-
wise, if pid is not a background process, exits without waiting for any processes to complete.
Because the system call must be executed in the parent process, the shell itself executes without creating a new process (see wait(2)).
Command-Line Arguments
supports the following command line arguments:
The unsigned decimal integer process
ID of a command, whose termination is to wait for.
WARNINGS
Some processes in a 2-or-more-stage pipeline may not be children of the shell, and thus cannot be waited for.
SEE ALSO
csh(1), ksh(1), sh-posix(1), sh(1), wait(2).
STANDARDS CONFORMANCE
wait(1)