Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Multiple Signals
Top Forums Programming Multiple Signals Post 34002 by Perderabo on Wednesday 29th of January 2003 11:53:02 AM
Old 01-29-2003
This is an odd thing to want. This is the way signals used to work and it was nasty.

You can still get the old behavior though. The details depend on which signal interface you are using. Posix is the way to go, so I'll assume that you're using that.

When you install your signal handler with sigaction(), specify the SA_NODEFER flag in the flags argument.

Then if your signal handler is running because you process got a signal, and another occurence of the same signal happens, your signal handler will be interrupted with another call to itself.

If you come to your senses and don't specify SA_NODEFER, then if your signal handler is running because your process got a signal, and another occurence of the same signal happens, the signal is deferred. When your handler returns, it will be called again to process the new signal.
 

10 More Discussions You Might Find Interesting

1. Programming

Signals In HP-UX

does the way of handling, interrupting signals in HP-UX same as that of solaris. If there is difference than what it is.?:confused: (1 Reply)
Discussion started by: kapilv
1 Replies

2. Programming

Threads Signals

Hi In my process there are few threads. Now, lets say all the threads are blocked for some reason or other.. now i read it somewhere that the kernel in this situation sends in some signal which can be caught. please let me know what signal is it and more details about that.. Thanks in... (1 Reply)
Discussion started by: uday_kumar_spl
1 Replies

3. UNIX for Dummies Questions & Answers

Signals...

(posted this in the scripting forum as well, but figured it should go here) So, what's going on is this: For our program, we had to create our own shell, and if the user pressed ctrl-c just at the cmdline, then this signal would be ignored, but if there is a foreground process running, let's... (0 Replies)
Discussion started by: blind melon
0 Replies

4. Programming

Using Signals

How can use signals in a C program If i want a child program to signal it's parent program that it(child) program has completed the task that it was assigned.:confused: (2 Replies)
Discussion started by: kapilv
2 Replies

5. UNIX for Dummies Questions & Answers

threads and signals

can any one give me an example of a concurrency program in threads and signals, i.e how to deliver messages between threads using signals. thanks (0 Replies)
Discussion started by: moe_7
0 Replies

6. Programming

threads and signals

can any one give me an example of a concurrency program in threads and signals, i.e how to deliver messages between threads using signals. thanks (2 Replies)
Discussion started by: moe_7
2 Replies

7. OS X (Apple)

How to debug signals

Hi, In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point. I am working on Mac X and using XCode. Thanks (0 Replies)
Discussion started by: Saurabh78
0 Replies

8. Programming

Can we debug Signals

Hi, In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point. I am working on Mac X and using XCode. Thanks (1 Reply)
Discussion started by: Saurabh78
1 Replies

9. Programming

C++ signals Linux

how can do this programs in c++ Program description: Infinite loop in a program starts working with 2 seconds the screen (console) "I 'm trying" to write, but it automatically after 10 seconds, the screen "Close" will terminate the execution of typing. c++ code (3 Replies)
Discussion started by: ss54
3 Replies

10. UNIX for Advanced & Expert Users

Help with Signals

Hi All, The problem statement is as below: Problem: A process (exe) is getting executed in background. The output of this process is getting logged in a file. After successfully running for some time the process gets terminated. In the log file following is present: ^M[7m Interrupt ^M[27m... (8 Replies)
Discussion started by: Praty.27
8 Replies

LEARN ABOUT REDHAT

kill

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

NAME

       kill - terminate a process

SYNOPSIS

       kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
       kill -l [ signal ]

DESCRIPTION

       The command kill sends the specified signal to the specified process or process group.  If no signal is specified, the TERM signal is sent.
       The TERM signal will kill processes which do not catch this signal.  For other processes, it may be necessary to use the KILL  (9)  signal,
       since this signal cannot be caught.

       Most  modern  shells  have  a  builtin  kill function, with a usage rather similar to that of the command described here. The `-a' and `-p'
       options, and the possibility to specify pids by command name is a local extension.

OPTIONS

       pid... Specify the list of processes that kill should signal.  Each pid can be one of five things:

	      n      where n is larger than 0.	The process with pid n will be signaled.

	      0      All processes in the current process group are signaled.

	      -1     All processes with pid larger than 1 will be signaled.

	      -n     where n is larger than 1.	All processes in process group n are signaled.	When an argument of the form `-n' is given, and it
		     is  meant	to  denote  a process group, either the signal must be specified first, or the argument must be preceded by a `--'
		     option, otherwise it will be taken as the signal to send.

	      commandname
		     All processes invoked using that name will be signaled.

       -s signal
	      Specify the signal to send.  The signal may be given as a signal name or number.

       -l     Print a list of signal names.  These are found in /usr/include/linux/signal.h

       -a     Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process.

       -p     Specify that kill should only print the process id (pid) of the named processes, and not send any signals.

SEE ALSO

       bash(1), tcsh(1), kill(2), sigvec(2), signal(7)

AUTHOR

       Taken from BSD 4.4.  The ability to translate process names to process ids was added by Salvatore Valente <svalente@mit.edu>.

Linux Utilities 						  14 October 1994							   KILL(1)
All times are GMT -4. The time now is 11:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy