How to block or ignore signals from certain processes? Post: 302233564

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:

2. UNIX for Advanced & Expert Users

Monitoring Processes - Killing hung processes

Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go? Thank you Richard

3. Solaris

Identifying and grouping OS processes and APP processes

Hi Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages. Any free tools or scripts to do this? Many thanks.

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

5. 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:

6. UNIX for Advanced & Expert Users

How to prevent gdb to send Interrupt signals to child processes

Hi, I have a program which invokes child processes and communicates with the processes. When I run the program under gdb and say interrupt, all the child processes are dying. Here I am not interested in debugging the child processes. But I don't want my child processes to be killed as my parent...

7. Programming

sending signals between two processes

Hello, I have two programs: server.c and client.c I need to send signal from client to server. As far as I know I need to use kill() function. To use kill() function I have to know the pid the second process. How can I send pid from process to process(both are written in separate files). ...

8. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can...

9. UNIX for Dummies Questions & Answers

Blocking signals

I know how to add signal to a set. But what if I want to add 2 or 3 signals to the set. I know I can use sigaddset (&set,SIGBUS)....but what if I want to add SIGBUS and SIGALRM at once. Do i have to do it like this.. sigaddset (&set,SIGBUS); sigaddset (&set,SIGALRM); Is there another way to...

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

LEARN ABOUT SUNOS

sigprocmask

sigprocmask(2)															    sigprocmask(2)

NAME

       sigprocmask - change or examine caller's signal mask

SYNOPSIS

       #include <signal.h>

       int sigprocmask(int how, const sigset_t *restrict set, sigset_t *restrict oset);

       The sigprocmask() function is used to examine and/or change the caller's signal mask. If the value is  SIG_BLOCK, the set pointed to by the
       set argument is added to the current signal mask. If the value is  SIG_UNBLOCK, the set pointed by the  set argument is	removed  from  the
       current	signal	mask. If the value is  SIG_SETMASK, the current signal mask is replaced by the set pointed to by the  set argument. If the
       oset argument is not  NULL, the previous mask is stored in the space pointed to by oset. If the value of the  set argument  is	NULL,  the
       value  how is not significant and the caller's signal mask is unchanged; thus, the call can be used to inquire about currently blocked sig-
       nals. If the set or oset argument points to an invalid address, the behavior is undefined and errno may be set to EFAULT.

       If there are any pending unblocked signals after the call to sigprocmask(), at least one of those signals will be delivered before the call
       to sigprocmask() returns.

       It  is  not possible to block signals that cannot be caught or ignored (see sigaction(2)). It is also not possible to block or unblock SIG-
       CANCEL, as SIGCANCEL is reserved for the implementation of POSIX thread cancellation (see  pthread_cancel(3C)  and  cancellation(5)).  This
       restriction is silently enforced by the standard C library.

       If sigprocmask() fails, the caller's signal mask is not changed.

       Upon successful completion, 0 is returned. Otherwise, -1 is returned and errno is set to indicate the error.

       The sigprocmask() function will fail if:

       EINVAL	       The value of the how argument is not equal to one of the defined values.

       The sigprocmask() function may fail if:

       EFAULT	       The set or oset argument points to an illegal address.

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard			   |
       +-----------------------------+-----------------------------+
       |MT-Level		     |Async-Signal-Safe 	   |
       +-----------------------------+-----------------------------+

       sigaction(2), pthread_cancel(3C), pthread_sigmask(3C), signal(3C), signal.h(3HEAD), sigsetops(3C), attributes(5), cancellation(5)

       The call to sigprocmask() affects only the calling thread's signal mask. It is identical to a call to pthread_sigmask(3C).

       Signals that are generated synchronously should not be masked. If such a signal is blocked and delivered, the receiving process is killed.

								    23 Mar 2005 						    sigprocmask(2)