Sponsored Content
Full Discussion: Kill Signal
Top Forums UNIX for Advanced & Expert Users Kill Signal Post 65797 by azmathshaikh on Wednesday 9th of March 2005 07:41:28 AM
Old 03-09-2005
I dont know the actual process, but the following info may help.

The kernel keeps record of all the processess running in the System in a process table. I dont know about other *nix, but Solaris keeps records of all processes in the directory /proc .

The shutdown behaviour depends on the application itself. If the appliction is written to handle signals like KILL, it will do some clean up as appropriate. Moreover, If the shutdown is initiated from the Scripts in init.d , it will always perform some clean up operation.

Also there is a system call kill which accepts pid & signal as an argument. If the pid is set to -1, it kills almost every process.

I've been working with Solaris for a few months now. So I am not sure if this is correct.

Bye
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

kill signal

Hello e'bdy, We have WebSphere MQ running on AIX 5.1 Every weekend MQ receives a kill -30 signal from some process or user and offloads a big error file. There is no way in MQ through which that process can be tracked. Is there something which i can do on UNIX level to trap the process? Best... (3 Replies)
Discussion started by: jhaavinash
3 Replies

2. UNIX for Advanced & Expert Users

When kill doesnt work, how to kill a process ?

Hi All, I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages. How can i terminate this daemon ? ? ? Regards, Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies

3. Programming

kill(0,-9) don't kill the process

Hi all i have simple c program , when i wish to kill the app im using kill(0,-9) , but it seams this command don't do any thing and the program. just ignore it . what im doing wrong here ? im using HP-UX ia64 Thanks (9 Replies)
Discussion started by: umen
9 Replies

4. UNIX for Advanced & Expert Users

Diff b/n kill and kill -9

Hi, I have a process with say pid x. What is the difference b/n kill x and kill -9 x in unix Thanks Ammu (2 Replies)
Discussion started by: ammu
2 Replies

5. Shell Programming and Scripting

Kill a process without using kill command

Sorry, posted the question in other forum. (0 Replies)
Discussion started by: sudhamacs
0 Replies

6. Linux

Kill a process without using kill command

I want to Kill a process without using kill command as i don't have privileges to kill the process. I know the pid and i am using Linux 2.6.9 OS. (6 Replies)
Discussion started by: sudhamacs
6 Replies

7. Shell Programming and Scripting

How to Trap kill -9 signal

I just want to trap kill -9 signal issued by any of user from any terminal and just capture that user terminal who had raised this kill -9 command (1 Reply)
Discussion started by: puneet.goel
1 Replies

8. UNIX for Dummies Questions & Answers

Meaning and typical use of -3 signal in kill

Hi, What is the use of the signal -3 in kill command in unix? I read the meaning and typical use of this signal in one of the Oreilly books as below. Quit -- stop running (and dump core). Sent when you type CTRL-\. what does the CTRL-\ command do? Is it the combination of CTRL and... (6 Replies)
Discussion started by: venkatesht
6 Replies

9. Solaris

Cannot kill a process with kill -9

Hello everyone, I have a process that I want to kill. I have tried kill-9 PID but it doesn't work. I have tried preap PID but it doesn't work too. The parent of my process is the process whose PID is 1, so I can't kill it. My OS is a Solaris 9. Can anyone help me understand what's going... (3 Replies)
Discussion started by: adilyos
3 Replies

10. Shell Programming and Scripting

Kill an specific process ID using the KILL and GREP commands

Good afternoon I need to KILL a process in a single command sentence, for example: kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'` That sentence Kills the process ID corresponding to the program CAL255.4ge. However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies
kill(1) 						      General Commands Manual							   kill(1)

NAME
kill - send a signal to a process; terminate a process SYNOPSIS
signame] pid ... signum] pid ... Obsolescent Versions: DESCRIPTION
The command sends a signal to each process specified by a pid process identifier. The default signal is which normally terminates pro- cesses that do not trap or ignore the signal. Options recognizes the following options: List all values of signame supported by the implementation. No signals are sent with this option. The symbolic names of the signals (without the prefix) are written to standard output, separated by spaces and newlines. Send the specified signal name. The default is number signame can be specified in upper- and/or lowercase, with or without the prefix. These val- ues can be obtained by using the option. The symbolic name represents signal value zero. See "Signal Names and Numbers" below. Send the specified decimal signal number. The default is See "Signal Names and Numbers" below. (Obsolescent.) Equivalent to (Obsolescent.) Equivalent to Operands pid is a process identifier, an unsigned or negative integer that can be one of the following: The number of a process. All processes, except special system processes, whose process group ID is equal to the process group ID of the sender. All processes, except special system processes, if the user has appropriate privileges. Otherwise, all processes, except special system processes, whose real or effective user ID is the same as the user ID of the sending process. All processes, except special system processes, whose process group ID is equal to the absolute value of pid and whose real or effective user ID is the same as the user of the sending process. Process numbers can be found with the command (see ps(1)) and with the built-in command available in some shells. Signal Names and Numbers The following table describes a few of the more common signals that can be useful from a terminal. For a complete list and a full descrip- tion, see the header file and the manual entry signal(5). signum signame Name Description ---------------------------------------------------------------------------- 0 SIGNULL Null Check access to pid 1 SIGHUP Hangup Terminate; can be trapped 2 SIGINT Interrupt Terminate; can be trapped 3 SIGQUIT Quit Terminate with core dump; can be trapped 9 SIGKILL Kill Forced termination; cannot be trapped 15 SIGTERM Terminate Terminate; can be trapped 24 SIGSTOP Stop Pause the process; cannot be trapped 25 SIGTSTP Terminal stop Pause the process; can be trapped 26 SIGCONT Continue Run a stopped process the null signal, invokes error checking but no signal is actually sent. This can be used to test the validity or existence of pid. the (default) terminate signal, can be trapped by the receiving process, allowing the receiver to execute an orderly shutdown or to ignore the signal entirely. For orderly operations, this is the preferred choice. the kill signal, forces a process to terminate immediately. Since cannot be trapped or ignored, it is useful for terminating a process that does not respond to The receiving process must belong to the user of the sending process, unless the user has appropriate privileges. As a single special case, the continue signal SIGCONT can be sent to any process that is a member of the same session as the sending process. RETURN VALUE
Upon completion, returns with one of the following values: At least one matching process was found for each pid operand, and the specified signal was successfully processed for at least one matching process. An error occurred. EXAMPLES
The command: signals process number 6135 to terminate. This gives the process an opportunity to exit gracefully (removing temporary files, etc.). The following equivalent commands: terminate process number 6135 abruptly by sending a signal to the process. This tells the kernel to remove the process immediately. WARNINGS
If a process hangs during some operation (such as I/O) so that it is never scheduled, it cannot die until it is allowed to run. Thus, such a process may never go away after the kill. Similarly, defunct processes (see ps(1)) may have already finished executing, but remain on the system until their parent reaps them (see wait(2)). Using to send signals to them has no effect. Some non-HP-UX implementations provide only as a shell built-in command. DEPENDENCIES
This manual entry describes the external command and the built-in command of the POSIX shell (see sh-posix(1)). Other shells, such as C and Korn (see csh(1) and ksh(1) respectively), also provide as a built-in command. The syntax for and output from these built-ins may be different. SEE ALSO
csh(1), ksh(1), ps(1), sh(1), sh-posix(1), kill(2), wait(2), signal(5). STANDARDS CONFORMANCE
kill(1)
All times are GMT -4. The time now is 11:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy