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
kill(2) System Calls Manual kill(2)
NAME
kill - Sends a signal to a process or to a group of processes
SYNOPSIS
#include <signal.h>
int kill(
pid_t process,
int signal );
Application developers may want to specify an #include statement for <sys/types.h> before the one for <signal.h> if programs are being
developed for multiple platforms. The additional #include statement is not required on Tru64 UNIX systems or by ISO or X/Open standards,
but may be required on other vendors' systems that conform to these standards.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
kill(): XSH5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
PARAMETERS
Specifies the process or group of processes. Specifies the signal. If the signal parameter is a value of 0 (the null signal), error check-
ing is performed but no signal is sent. This can be used to check the validity of the process parameter.
DESCRIPTION
The kill() function sends the signal specified by the signal parameter to the process or group of processes specified by the process param-
eter.
To send a signal to another process, at least one of the following must be true: The real or the saved set-user-ID of the sending process
matches the real or effective user ID of the receiving process. The process is trying to send the SIGCONT signal to one of its session's
processes. The calling process has root privileges.
Processes can send signals to themselves.
Sending a signal does not imply that the operation is successful. All signal operations must pass the access checks prescribed by each
enforced access control policy on the system.
If the process parameter is greater than 0 (zero), the signal specified by the signal parameter is sent to the process that has a process
ID equal to the value of the process parameter.
If the process parameter is equal to 0 (zero), the signal specified by the signal parameter is sent to all of the processes (other than
system processes) whose process group ID is equal to the process group ID of the sender.
If the process parameter is equal to -1, the signal specified by the signal parameter is sent to all of the processes other than system
processes for which the process has permission to send that signal. For example, if the effective user ID of the sender has root privi-
leges, the signal specified by the signal parameter is sent to all of the processes other than system processes.
If the process parameter is negative but not -1, the signal specified by the signal parameter is sent to all of the processes which have a
process group ID equal to the absolute value of the process parameter.
RETURN VALUES
Upon successful completion, the kill() function returns a value of 0 (zero). Otherwise, a value of -1 is returned and errno is set to indi-
cate the error.
NOTES
Some applications and scripts depend on the process ID of the init program being 1 (one): do not depend on it. Instead, use standard
methods, such as the ps and grep commands, to obtain all process IDs.
ERRORS
The kill() function sets errno to the specified values for the following conditions: The signal parameter is not a valid signal number.
[Tru64 UNIX] The signal parameter is SIGKILL, SIGSTOP, SIGTSTP or SIGCONT and the process parameter is the process ID of the init
program. No process or process group can be found corresponding to that specified by the process parameter. The real or saved user
ID does not match the real or effective user ID of the receiving process, the calling process does not have appropriate privilege,
and the process is not sending a SIGCONT signal to one of its session's processes. [Tru64 UNIX] The calling process does not have
appropriate privilege.
RELATED INFORMATION
Functions: getpid(2), killpg(2), raise(3), setpgid(2), sigaction(2), sigvec(2)
Standards: standards(5) delim off
kill(2)