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

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 LINUX

ssetmask

SGETMASK(2)						     Linux Programmer's Manual						       SGETMASK(2)

NAME

       sgetmask, ssetmask - manipulation of signal mask (obsolete)

SYNOPSIS

       long sgetmask(void);

       long ssetmask(long newmask);

DESCRIPTION

       These system calls are obsolete.  Do not use them; use sigprocmask(2) instead.

       sgetmask() returns the signal mask of the calling process.

       ssetmask() sets the signal mask of the calling process to the value given in newmask.  The previous signal mask is returned.

       The  signal  masks dealt with by these two system calls are plain bit masks (unlike the sigset_t used by sigprocmask(2)); use sigmask(3) to
       create and inspect these masks.

RETURN VALUE

       sgetmask() always successfully returns the signal mask.	ssetmask() always succeeds, and returns the previous signal mask.

ERRORS

       These system calls always succeed.

CONFORMING TO

       These system calls are Linux-specific.

NOTES

       Glibc does not provide wrappers for these system calls; use syscall(2).

       These system calls are unaware of signal numbers greater than 31 (i.e., real-time signals).

       It is not possible to block SIGSTOP or SIGKILL.

SEE ALSO

       sigprocmask(2), signal(7)

COLOPHON

       This page is part of release 3.27 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

Linux								    2007-07-05							       SGETMASK(2)