Section 1.9. Signals

1.9. Signals

Signals are a technique used to notify a process that some condition has occurred. For example, if a process divides by zero, the signal whose name is SIGFPE (floating-point exception) is sent to the process. The process has three choices for dealing with the signal.

1. Ignore the signal. This option isn't recommended for signals that denote a hardware exception, such as dividing by zero or referencing memory outside the address space of the process, as the results are undefined.

2. Let the default action occur. For a divide-by-zero condition, the default is to terminate the process.

3. Provide a function that is called when the signal occurs (this is called "catching" the signal). By providing a function of our own, we'll know when the signal occurs and we can handle it as we wish.

Many conditions generate signals. Two terminal keys, called the interrupt key often the DELETE key or Control-Cand the quit keyoften Control-backslashare used to interrupt the currently running process. Another way to generate a signal is by calling the kill function. We can call this function from a process to send a signal to another process. Naturally, there are limitations: we have to be the owner of the other process (or the superuser) to be able to send it a signal.

Example

Recall the bare-bones shell example (Figure 1.7). If we invoke this program and press the interrupt key, the process terminates because the default action for this signal, named SIGINT, is to terminate the process. The process hasn't told the kernel to do anything other than the default with this signal, so the process terminates.

To catch this signal, the program needs to call the signal function, specifying the name of the function to call when the SIGINT signal is generated. The function is named sig_int; when it's called, it just prints a message and a new prompt. Adding 11 lines to the program in Figure 1.7 gives us the version in Figure 1.10. (The 11 new lines are indicated with a plus sign at the beginning of the line.)

In Chapter 10, we'll take a long look at signals, as most nontrivial applications deal with them.

Figure 1.10. Read commands from standard input and execute them

   #include "apue.h"   #include <sys/wait.h> + static void sig_int(int);       /* our signal-catching function */ +   int   main(void)   {       char    buf[MAXLINE];    /* from apue.h */       pid_t   pid;       int     status; +     if (signal(SIGINT, sig_int) == SIG_ERR) +         err_sys("signal error"); +       printf("%% ");  /* print prompt (printf requires %% to print %) */       while (fgets(buf, MAXLINE, stdin) != NULL) {           if (buf[strlen(buf) - 1] == "\n")               buf[strlen(buf) - 1] = 0; /* replace newline with null */           if ((pid = fork()) < 0) {               err_sys("fork error");           } else if (pid == 0) {        /* child */               execlp(buf, buf, (char *)0);               err_ret("couldn't execute: %s", buf);               exit(127);           }           /* parent */           if ((pid = waitpid(pid, &status, 0)) < 0)               err_sys("waitpid error");           printf("%% ");       }       exit(0);   } + + void + sig_int(int signo) + { +     printf("interrupt\n%% "); + }