Sponsored Content
Full Discussion: Signals...
Top Forums UNIX for Dummies Questions & Answers Signals... Post 302255147 by blind melon on Thursday 6th of November 2008 02:08:15 AM
Old 11-06-2008
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 say, "sleep 10", and ctrl-c was pressed, then this process would be terminated... however, my problem lies within background processes... when I press ctrl-c after running something like "sleep 10 &", where the '&' indicates it's a background process, it uses the correct if branch of my SIGINT_handler, but it terminates the process.... so it's definitely something wrong with either the handler, or the installation of the signal.

What I don't get is... if the ctrl-c at the command line doesn't quit the program, why would it terminate my background process? Is it because the parent process just puts the ctrl-c onto the child processes? If so, is there a way to add something to my SIGINT_handler to make it ignore this signal?

****Let me just say that I have successfully been able to ignore the signal for a background process, but this way doesn't use my SIGINT_handler, which I do want it to use so some text gets printed. The way I'm talking of is just using "signal(SIGINT, SIG_IGN)", but like I said, doesn't use my SIGINT_handler...


This is my SIGINT_handler:

void SIGINT_handler(int sig)
{
if (foreground_pid == 0)
{
fprintf(stderr, "\nSIGINT ignored\n");
}
else
{
kill(foreground_pid, SIGINT);
foreground_pid = 0;
}
}


And then when I install the handler/signal, I use signal(SIGINT, SIGINT_handler) and also set foreground_pid in its respective spot... so if anyone can help, that'd be awesome, and if you need to see more code or some things are unclear, ask. Thanks.
 

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

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

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

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

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

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

7. UNIX for Dummies Questions & Answers

Help understanding signals

I am having trouble with folowing sigset_t s; // now s represents set of signals sigemptyset(&s) ; // initialize this set and exclude all the signals from it.is it empty? sigaddset(&s,SIGILL);//this set containts only SIGILL signal sigprocmask(SIG_BLOCK,&s,NULL);//lost on this one Can... (3 Replies)
Discussion started by: joker40
3 Replies

8. UNIX for Dummies Questions & Answers

perror with signals

I have following problem with this code.. First time trough the main loop..... perror gives ....blocked signal:success(all other times gives illlegal seek) Should every time trought the main loop be success?? And the perror otside of main loop...didn't change mask:success That line of code... (2 Replies)
Discussion started by: joker40
2 Replies

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... (0 Replies)
Discussion started by: joker40
0 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
signal(3C)						   Standard C Library Functions 						signal(3C)

NAME
signal, sigset, sighold, sigrelse, sigignore, sigpause - simplified signal management for application processes SYNOPSIS
#include <signal.h> void (*signal(int sig, void (*disp)(int)))(int); void (*sigset(int sig, void (*disp)(int)))(int); int sighold(int sig); int sigrelse(int sig); int sigignore(int sig); int sigpause(int sig); DESCRIPTION
These functions provide simplified signal management for application processes. See signal.h(3HEAD) for an explanation of general signal concepts. The signal() and sigset() functions modify signal dispositions. The sig argument specifies the signal, which may be any signal except SIGKILL and SIGSTOP. The disp argument specifies the signal's disposition, which may be SIG_DFL, SIG_IGN, or the address of a signal han- dler. If signal() is used, disp is the address of a signal handler, and sig is not SIGILL, SIGTRAP, or SIGPWR, the system first sets the signal's disposition to SIG_DFL before executing the signal handler. If sigset() is used and disp is the address of a signal handler, the system adds sig to the calling process's signal mask before executing the signal handler; when the signal handler returns, the system restores the calling process's signal mask to its state prior to the delivery of the signal. In addition, if sigset() is used and disp is equal to SIG_HOLD, sig is added to the calling process's signal mask and the signal's disposition remains unchanged. The sighold() function adds sig to the calling process's signal mask. The sigrelse() function removes sig from the calling process's signal mask. The sigignore() function sets the disposition of sig to SIG_IGN. The sigpause() function removes sig from the calling process's signal mask and suspends the calling process until a signal is received. RETURN VALUES
Upon successful completion, signal() returns the signal's previous disposition. Otherwise, it returns SIG_ERR and sets errno to indicate the error. Upon successful completion, sigset() returns SIG_HOLD if the signal had been blocked or the signal's previous disposition if it had not been blocked. Otherwise, it returns SIG_ERR and sets errno to indicate the error. Upon successful completion, sighold(), sigrelse(), sigignore(), and sigpause(), return 0. Otherwise, they return -1 and set errno to indicate the error. ERRORS
These functions fail if: EINTR A signal was caught during the execution sigpause(). EINVAL The value of the sig argument is not a valid signal or is equal to SIGKILL or SIGSTOP. USAGE
The sighold() function used in conjunction with sigrelse() or sigpause() may be used to establish critical regions of code that require the delivery of a signal to be temporarily deferred. If signal() or sigset() is used to set SIGCHLD's disposition to a signal handler, SIGCHLD will not be sent when the calling process's children are stopped or continued. If any of the above functions are used to set SIGCHLD's disposition to SIG_IGN, the calling process's child processes will not create zom- bie processes when they terminate (see exit(2)). If the calling process subsequently waits for its children, it blocks until all of its children terminate; it then returns -1 with errno set to ECHILD (see wait(3C) and waitid(2)). The system guarantees that if more than one instance of the same signal is generated to a process, at least one signal will be received. It does not guarantee the reception of every generated signal. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
exit(2), kill(2), pause(2), sigaction(2), sigsend(2), waitid(2), signal.h(3HEAD), wait(3C), attributes(5), standards(5) SunOS 5.11 6 Sep 2007 signal(3C)
All times are GMT -4. The time now is 08:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy