signals - SIGTERM Post: 8926

9 More Discussions You Might Find Interesting

1. HP-UX

make fuser send SIGTERM?

Hello, Nice forum BTW... anyway on to my question. I am trying to write a korn shell script that will shut down a java VM. The first challenge was how to figure out which java VM to kill, as there can be other java processes running at the same time. Then I discovered fuser. It says it...

2. Programming

How to implement SIGKILL and SIGTERM and print a message?

Hello, I am running a webserver that uses sockets, forks, and children. The parent process listens for connections and the child processes the information. I am trying to figure out why the code I have below SIGTERM, and SIGKILL never fire. I was messing around with the printfs and doesnt...

3. Programming

Can SIGTERM to main process kill the detached threads?

Hi, I am stuck up with a strange problem. I am writing an application - a kinda tracker that reads data from memcache and invokes theads to process each record of the memcache. I dont want to join all my threads because my tracker should poll the cache in regular intervals say sum 300...

4. Programming

the parent receive SIGTERM from its child (httpd) ?

the parent is a process manager in our design, and httpd service is one of its child processes, which is started in foreground mode (with "-D FOREGROUND" options) according to our requirements. when httpd service is started, one main httpd process and eight sub httpd processes can be found by...

5. Shell Programming and Scripting

How to detect SIGTERM,SIGKILL signal in UNIX

Dear All We have JBOSS server running on Linux we need to track Graceful Shutdown(SIGTERM) and Forceful Shutdown(SIGKILL) timestamp and write it into one file, I am new to UNIX Signal processing if is it possible how to detect it? We generally do $kill PID For Graceful...

6. Programming

Reliable management of signal SIGPIPE and SIGTERM

I' m note very expert in the reliable manage of signal... but in my server I must manage SIGPIPE for the socket and SIGTERM... I've wrote this but there is something wrong... Can someone explain me with some example the reliable management of signal?? This is what I've wrote in the server ...

7. Shell Programming and Scripting

Current instance of Shell ignoring SIGTERM

Hello. Could anyone tell me how can I configure a instance of Shell to ignore the SIGTERM signal? I would really appreciate. Thanks.

8. Shell Programming and Scripting

ksh child process not ignoring SIGTERM

My ksh version is ksh93- =>rpm -qa | grep ksh ksh-20100621-3.fc13.i686 I have a simple script which is as below - #cat test_sigterm.sh - #!/bin/ksh trap 'echo "removing"' QUIT while read line do sleep 20 done I am Executing the script From Terminal 1 - 1. The ksh is started...

9. AIX

SIGTERM failing in AIX

I have 2 AIX 6.1 systems running on PowerPCs - production and .. .everything else. :p . Until the installation of a TLS certificate in an application, some copying of files ("cloning an environment") and upgrading a listener, sending a kill -15 worked on any script/application, so long as we were...

LEARN ABOUT LINUX

kill

KILL(1) 							Linux User's Manual							   KILL(1)

NAME

       kill - send a signal to a process

SYNOPSIS

       kill [ -signal | -s signal ] pid ...
       kill [ -L | -V, --version ]
       kill -l	[ signal ]

DESCRIPTION

       The  default  signal  for  kill is TERM. Use -l or -L to list available signals.  Particularly useful signals include HUP, INT, KILL, STOP,
       CONT, and 0.  Alternate signals may be specified in three ways: -9 -SIGKILL -KILL.  Negative PID values may be used to choose whole process
       groups;	see  the  PGID	column in ps command output. A PID of -1 is special; it indicates all processes except the kill process itself and
       init.

SIGNALS

       The signals listed below may be available for use with kill.  When known constant, numbers and default behavior are shown.

       Name	Num   Action	Description
       0	  0   n/a	exit code indicates if a signal may be sent
       ALRM	 14   exit
       HUP	  1   exit
       INT	  2   exit
       KILL	  9   exit	cannot be blocked
       PIPE	 13   exit
       POLL	      exit
       PROF	      exit
       TERM	 15   exit
       USR1	      exit
       USR2	      exit
       VTALRM	      exit
       STKFLT	      exit	might not be implemented
       PWR	      ignore	might exit on some systems
       WINCH	      ignore
       CHLD	      ignore
       URG	      ignore
       TSTP	      stop	might interact with the shell
       TTIN	      stop	might interact with the shell
       TTOU	      stop	might interact with the shell
       STOP	      stop	cannot be blocked
       CONT	      restart	continue if stopped, otherwise ignore
       ABRT	  6   core
       FPE	  8   core
       ILL	  4   core
       QUIT	  3   core
       SEGV	 11   core
       TRAP	  5   core
       SYS	      core	might not be implemented
       EMT	      core	might not be implemented
       BUS	      core	core dump might fail
       XCPU	      core	core dump might fail
       XFSZ	      core	core dump might fail

NOTES

       Your shell (command line interpreter) may have a built-in kill command.	You may need to run the command described  here  as  /bin/kill	to
       solve the conflict.

EXAMPLES

       kill -9 -1
	      Kill all processes you can kill.

       kill -l 11
	      Translate number 11 into a signal name.

       kill -L
	      List the available signal choices in a nice table.

       kill 123 543 2341 3453
	      Send the default signal, SIGTERM, to all those processes.

SEE ALSO

       pkill(1), skill(1), kill(2), renice(1), nice(1), signal(7), killall(1).

STANDARDS

       This command meets appropriate standards. The -L flag is Linux-specific.

AUTHOR

       Albert  Cahalan	<albert@users.sf.net>  wrote  kill  in 1999 to replace a bsdutils one that was not standards compliant. The util-linux one
       might also work correctly.

       Please send bug reports to <procps-feedback@lists.sf.net>

Linux								 November 21, 1999							   KILL(1)