Script Signal Processing Post: 302263309

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Signal Processing

Hello, Can any body give example of using Unix Signals. What I want to do is I am running a sql query in a shell script I want, if sql query exceed the defined no. of seconds limit, then I would like to kill the process. I know this can be done thru Unix Signal Handling but I do not know...

2. Shell Programming and Scripting

signal script?

I have a script which invoke a java program, because the program requires file as input, hence the script would sleep a X seconds then check for file existence, if the file exists then program is invoker else, keep waiting until the time is up. My problem is that if there is a way to find out if my...

3. Programming

Signal processing

We have written a deamon which have many threads. We are registering for the SIGTERM and trying to close main thread in this signal handling. Actually these are running on Mac OS X ( BSD unix). When we are unloading the deamon with command launchctl, it's sending SIGTERM signal to our process...

4. Programming

alarm signal processing

I'm writing a function right now, and I want to set an alarm to avoid a timeout, here's the general idea of my code: int amt = -2; alarm(10); amt = read(fd, &t->buf, TASKBUFSIZ - tailpos); //do a read when the alarm goes off, i want to check the value of "amt" ...

5. Solaris

Signal Processing in unix

I've read the man page of singal(3) but I still can't quite understand what is the difference between SIGINT, SIGALRM and SIGTERM. Can someone tell me what is the behavioral difference among these 3 signals in kill command? Thanks!

6. Programming

awk processing / Shell Script Processing to remove columns text file

Hello, I extracted a list of files in a directory with the command ls . However this is not my computer, so the ls functionality has been revamped so that it gives the filesizes in front like this : This is the output of ls command : I stored the output in a file filelist 1.1M...

7. Shell Programming and Scripting

Continue Processing after a signal is caught

Is it possible to continue after signal is caught and control goes to function specified in the trap statement?

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)