08-26-2001
creating new signals
Hello,
My first question to you would be...
why do you want to create a new signal?
Can you expand on your reasoning for doing so?
In the 2.2.X kernel, you currently have all
the POSIX.1 signals along with some 17 or so
other signals supported. In general, I would
not recommend making changes to signal.c unless
you're trying to fix a bug. By adding a new
signal to the kernel, you effectively have
created a new "experimental" version of your
kernel and future kernel upgrades would have
to also be modified.
10 More Discussions You Might Find Interesting
1. Programming
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. UNIX for Dummies Questions & Answers
(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
3. Programming
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
4. Programming
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
5. Programming
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
6. UNIX for Dummies Questions & Answers
Greetings,
I am writing a small program in C on UNIX, in which I am using (POSIX reliable) signals.
1. Suppose I have a signal : SIGX, and the corresponding signal handler : sigx_handler.
It is possible to receive SIGX in my process, and, while executing sigx_handler, to receive
again... (0 Replies)
Discussion started by: aigoia
0 Replies
7. AIX
I am in process of writing a library which can make any application of my product capable of creating core in the application's log folder with a product friendly core file name programatically. In my library I am registering for certain signals e.g. SIGILL, SIGFPE, SIGBUS, SIGSEGV, SIGSYS, SIGABRT... (1 Reply)
Discussion started by: rajeev_ks
1 Replies
8. Solaris
I am in process of writing a library which can make any application of my product capable of creating core in the application's log folder with a product friendly core file name programatically. In my library I am registering for certain signals e.g. SIGILL, SIGFPE, SIGBUS, SIGSEGV, SIGSYS, SIGABRT... (5 Replies)
Discussion started by: rajeev_ks
5 Replies
9. UNIX for Advanced & Expert Users
What will happen if signal comes while a system call is being executed?
How it will be handled? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
10. UNIX for Advanced & Expert Users
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
pause(2) System Calls Manual pause(2)
NAME
pause - suspend process until signal
SYNOPSIS
DESCRIPTION
suspends the calling process until it receives a signal. The signal must be one that is not currently set to be ignored or blocked
(masked) by the calling process.
If the signal causes termination of the calling process, does not return.
If the signal is by the calling process and control is returned from the signal-catching function (see signal(5)), the calling process
resumes execution from the point of suspension; with a return value of -1 from and set to
APPLICATION USAGE
Threads Considerations
Signal dispositions (such as catch/default/ignore) are shared by all threads in the process and blocked signal masks are maintained by each
thread. Therefore, the signals being waited for should not be ignored by the process or blocked by the calling thread.
will suspend only the calling thread until it receives a signal.
If other threads in the process do not block the signal, the signal may be delivered to another thread in the process and the thread in may
continue waiting. For this reason, the use of is recommended instead of for multi-threaded applications.
For more information regarding signals and threads, refer to signal(5).
SEE ALSO
alarm(2), kill(2), sigwait(2), wait(2), signal(5).
STANDARDS CONFORMANCE
pause(2)