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:
with the above code, only the number printed. I would like to get the name of the signal... i'm hoping that there is a built-in function for me to get this so that i won't need to manually code the conversion part in.
Also, do i need to have ( signal(SIGINT, handler); ) and a handler function set for EVERY signal that I want to catch? Is there a way for me to catch all the signals using one handler? would the use of sigaction() and sigprocmask() satisfy my requirements?
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)
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)
I am using the signal function, and passing it a function named quit procedure...I get the following warning....
passing arg2 of signal from incompatible pointer type...
void quit_procedure(void); //this is the way i define my prototype...
signal(SIGINT, quit_procedure);
Please guide... (5 Replies)
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)
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)
I'am expecting a signal, but no signal is received when the stack-size reaches 10 bytes.
Here in this code i'am setting rlim_cur=10bytes.
To be more precise, when it reaches 10 bytes the process must receive a SIGSEGV signal? But i find no signal being received.
Am i missing something in this... (0 Replies)
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... (1 Reply)
Hi,
I am basically new to signals in UNIX. My question is, should the signal() command be called only once in the program? What will happen if it's called multiple times? I am trying to write an alarm program where the signal handler function changes in runtime. It just doesn't work if I... (2 Replies)
Sun Solaris Unix Question
Haven't been able to find any solution for this situation. Let's just say the file names listed below exist in a directory. I want the find command to find all files in this directory but at the same time I want to eliminate certain file names or files with certain... (2 Replies)
Data files coming in different names in a file name called process.txt.
1. shipments_yyyymmdd.gz
2 Order_yyyymmdd.gz
3. Invoice_yyyymmdd.gz
4. globalorder_yyyymmdd.gz
The process needs to discard all the below files and only process two of the 4 file names available
... (1 Reply)
Discussion started by: dsravanam
1 Replies
LEARN ABOUT HPUX
pause
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)