04-13-2005
Yes, you are right about the killing of all processes with PPID of 1. My problem initially stems from my oracle application server report printing. Every day there are about 50 processes left hanging after the batch printing finishes
example:
oracle 5321 1 0 Apr 04 ? 0:00 lp -d rp_h1-batch2_lp
So what I really want is to specify that this type of process be cleaned up. Right now I have to manually do them every few days. I could match up the character string of rp_h1, which is what I do with my grep statement in my initial posting, that way I would not eleminate any processes uneccesarily.
That was why I was doing the grep and excluding root and specifying a character string then writing to a file. I'm going to mess around with Ice's suggestions and see what I can come up with. Thanks and further advice will be appreciated!!
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Friends,
I need to write a script to kill some processes running for more than 10 minutes. Can I get some pointers on that. Thanks for ur help in Advance.
Thanks&Regards,
Amit (1 Reply)
Discussion started by: amitsayshii
1 Replies
2. Shell Programming and Scripting
Hi Friends,
I need to write a script to kill some processes running for more than 10 minutes. Can I get some pointers on that. Thanks for ur help in Advance.
Thanks&Regards,
Amit (1 Reply)
Discussion started by: amitsayshii
1 Replies
3. UNIX for Dummies Questions & Answers
Hi Friends,
I need to write a script to kill some processes running for more than 10 minutes. Can I get some pointers on that. Thanks for ur help in Advance.
Thanks&Regards,
Amit (3 Replies)
Discussion started by: amitsayshii
3 Replies
4. 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
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. UNIX for Dummies Questions & Answers
hi guys,
can anyone help me out with the script to kill all the related process at once.
i have something like below
ps -fu
UID PID PPID C STIME TTY TIME CMD
xyz 17398 1 2 Dec30 ? 00:31:20 ./psa_mux -simulate -client_ports 22000
xyz 17399 1 2... (2 Replies)
Discussion started by: smithaph
2 Replies
7. 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
8. Shell Programming and Scripting
Hi,
when i grep for the process "XYZ" , there will be some good number of processes with that name, i want to kill all the these processes at a time using shell script?
Any help needed for this action.
Thanks
Regards,
Anil (6 Replies)
Discussion started by: anilmanepu
6 Replies
9. Shell Programming and Scripting
my unix machine is currently shared by many teams, because of that lots of processess are running and bad part is taht when I do psu ...i can see all tail processes as well , meaning ppl who have viewed files with tail and have forgotten to close it.
command prompt >> psu
tail -n 0 -f... (2 Replies)
Discussion started by: mitsyjohn
2 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
killall(8) System Manager's Manual killall(8)
NAME
killall - Terminates all processes started by the user, except the calling process
SYNOPSIS
/usr/sbin/killall [- | [-]signal_name | -signal_number]
/usr/sbin/killall -l
FLAGS
The hyphen character (without an argument) sends a SIGTERM signal initially and then sends a SIGKILL signal to all processes that survive
for 30 seconds after receipt of the first signal. This gives processes that catch the SIGTERM signal an opportunity to clean up. A signal
name, optionally preceded by a hyphen, sends the specified signal to processes. The hyphen character (with a signal number argument) sends
the specified signal, either a name, stripped of the SIG prefix (such as KILL), or a number (such as 9). For information about signal
names and numbers, see the signal() system call.
In the System V habitat, the optional signal number does not have to be preceded with a hyphen (-). Lists signal names in numerical order
(as given in the /usr/include/signal.h file), stripped of the common SIG prefix.
DESCRIPTION
This command provides a convenient means of killing all processes created by the shell that you control. When started by the superuser,
the killall command kills all processes that can be terminated, except those processes that started it, the kernel processes, and processes
0 and 1 (init).
Security Configuration
This command is modified in all security configurations of the system.
EXAMPLES
To stop all background processes that have started, enter: killall This sends all background processes signal 9 (the kill signal, also
called SIGKILL). To stop all background processes, giving them a chance to clean up, enter: killall - This sends signal 15 (SIGTERM),
waits 30 seconds, and then sends signal 9 (SIGKILL). To send a specific signal to the background processes, enter: killall -2 This sends
signal 2 (SIGINT) to the background processes. To list the signal names in numerical order, stripped of the SIG prefix, enter: killall -l
This displays a list of signals, which may vary from system to system.
FILES
Specifies the command path
RELATED INFORMATION
Calls: kill(2), sigaction(2), signal(2) delim off
killall(8)