Sponsored Content
Full Discussion: Trying to block signal
Top Forums UNIX for Dummies Questions & Answers Trying to block signal Post 302465044 by DGPickett on Thursday 21st of October 2010 02:25:47 PM
Old 10-21-2010
Moderator's Comments:
Mod Comment Unix/Linux Man Pages are found here, on our site. Please use them in these forums.


Code:
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  pro-
       cess  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	this signal may not be blocked
       PIPE	 13   exit
       POLL	      exit
       PROF	      exit
       TERM	 15   exit
       USR1	      exit
       USR2	      exit
       VTALRM	      exit
       STKFLT	      exit	may not be implemented
       PWR	      ignore	may exit on some systems
       WINCH	      ignore
       CHLD	      ignore
       URG	      ignore
       TSTP	      stop	may interact with the shell
       TTIN	      stop	may interact with the shell
       TTOU	      stop	may interact with the shell
       STOP	      stop	this signal may not be blocked
 .
 .
 .
 .

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Alarm signal

Hi, when I execute a script on unix AIX, I've got an error message: "Execution: 85328 Signal d'alarme". If I edit this file with "vi", I ve got the same error after a while (about 1 minute). If I try with another user I still have the problem. But if I rename this file, no problem. My... (5 Replies)
Discussion started by: cgsteph
5 Replies

2. Programming

Signal Names

Hi everyone, Is there a variable or built in function in the Unix env. for me to obtain the name of a signal that is caught? As far as I understand only a numeric value of the signal is returned to the handler. For example: void handler (int signum) { ... (2 Replies)
Discussion started by: laila63
2 Replies

3. 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

4. UNIX for Advanced & Expert Users

Kill Signal

Hello, I'm doing a project of OS simulation (Process Scheduling, to be very specific). Can anyone, please, explain what exactly happens in the background when we see "Sending all processes the KILL signal...........". How is it sent to each process? Is it that something like a boolean is stored... (3 Replies)
Discussion started by: ameya
3 Replies

5. Shell Programming and Scripting

Signal question

Who can explain the meaning of the &2 &1 or @, #, etc in the script? Is there any document which can explain the usage of these words in details? for example: ls /etc/sysconfig/network > /dev/null 2>&1 #@ bash, ksh and sh. Thanks in advance for ur advice. (1 Reply)
Discussion started by: GCTEII
1 Replies

6. 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... (1 Reply)
Discussion started by: mpang_
1 Replies

7. Programming

Signal catching

Hi! I want to catch all signals that my program receives print their name and then execute the default handler. Can you help me on that? I've tried the following code: #include <stdio.h> #include <unistd.h> #include <signal.h> void (*hnd)(int i); char signals = { "SIGHUP",... (7 Replies)
Discussion started by: dark_knight
7 Replies

8. Shell Programming and Scripting

Killed by signal 15.

Hi all I have Master script, Main script ,and 4 Child script. Master.sh #!/bin/bash /export/home/user/Main.shMain.sh #!/bin/bash /export/home/user/Child1.sh & /export/home/user/Child2.sh & /export/home/user/Child3.sh & /export/home/user/Child4.sh &I run only Master.sh script... (1 Reply)
Discussion started by: almanto
1 Replies

9. Programming

queue a signal

A program have to receive signals and work agreed with it, but the process have to receive more than one signal when it is attending other. Those have to be queued to be attended later recived. how can i do that? thanks. (2 Replies)
Discussion started by: marmaster
2 Replies

10. Programming

Signal function

Hello I want to know how can i use signal function in c for keyboard interrupt handling. what i exactly want is : my program is processing and if i press any key while processing , the program should call the interrupt and displays/prints that key and now goes back to processing. I added the... (5 Replies)
Discussion started by: Jahanzeb
5 Replies
SKILL(1)							Linux User's Manual							  SKILL(1)

NAME
skill, snice - send a signal or report process status SYNOPSIS
skill [signal to send] [options] process selection criteria snice [new priority] [options] process selection criteria DESCRIPTION
These tools are probably obsolete and unportable. The command syntax is poorly defined. Consider using the killall, pkill, and pgrep com- mands instead. The default signal for skill 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. The default priority for snice is +4. (snice +4 ...) Priority numbers range from +20 (slowest) to -20 (fastest). Negative priority num- bers are restricted to administrative users. GENERAL OPTIONS
-f fast mode This is not currently useful. -i interactive use You will be asked to approve each action. -v verbose output Display information about selected processes. -w warnings enabled This is not currently useful. -n no action This only displays the process ID. -V show version Displays version of program. PROCESS SELECTION OPTIONS
Selection criteria can be: terminal, user, pid, command. The options below may be used to ensure correct interpretation. Do not blame Albert for this interesting interface. -t The next argument is a terminal (tty or pty). -u The next argument is a username. -p The next argument is a process ID number. -c The next argument is a command name. SIGNALS
The signals listed below may be available for use with skill. When known, 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 this signal may not be blocked PIPE 13 exit POLL exit PROF exit TERM 15 exit USR1 exit USR2 exit VTALRM exit STKFLT exit may not be implemented PWR ignore may exit on some systems WINCH ignore CHLD ignore URG ignore TSTP stop may interact with the shell TTIN stop may interact with the shell TTOU stop may interact with the shell STOP stop this signal may not 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 may not be implemented EMT core may not be implemented BUS core core dump may fail XCPU core core dump may fail XFSZ core core dump may fail EXAMPLES
Command Description snice seti crack +7 Slow down seti and crack skill -KILL -v /dev/pts/* Kill users on new-style PTY devices skill -STOP viro lm davem Stop 3 users snice -17 root bash Give priority to root's shell SEE ALSO
killall(1), pkill(1), kill(1), renice(1), nice(1), kill(2), signal(7) STANDARDS
No standards apply. AUTHOR
Albert Cahalan <albert@users.sf.net> wrote skill and snice in 1999 as a replacement for a non-free version, and is the current maintainer of the procps collection. Please send bug reports to <procps-feedback@lists.sf.net>. Linux March 12, 1999 SKILL(1)
All times are GMT -4. The time now is 10:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy