Launching Jobs - The GNU C Library

Next: Foreground and Background, Previous: Initializing the Shell, Up: Implementing a Shell

#### 27.6.3 Launching Jobs

Once the shell has taken responsibility for performing job control on its controlling terminal, it can launch jobs in response to commands typed by the user.

To create the processes in a process group, you use the same `fork` and `exec` functions described in Process Creation Concepts. Since there are multiple child processes involved, though, things are a little more complicated and you must be careful to do things in the right order. Otherwise, nasty race conditions can result.

You have two choices for how to structure the tree of parent-child relationships among the processes. You can either make all the processes in the process group be children of the shell process, or you can make one process in group be the ancestor of all the other processes in that group. The sample shell program presented in this chapter uses the first approach because it makes bookkeeping somewhat simpler.

As each process is forked, it should put itself in the new process group by calling `setpgid`; see Process Group Functions. The first process in the new group becomes its process group leader, and its process ID becomes the process group ID for the group.

The shell should also call `setpgid` to put each of its child processes into the new process group. This is because there is a potential timing problem: each child process must be put in the process group before it begins executing a new program, and the shell depends on having all the child processes in the group before it continues executing. If both the child processes and the shell call `setpgid`, this ensures that the right things happen no matter which process gets to it first.

If the job is being launched as a foreground job, the new process group also needs to be put into the foreground on the controlling terminal using `tcsetpgrp`. Again, this should be done by the shell as well as by each of its child processes, to avoid race conditions.

The next thing each child process should do is to reset its signal actions.

During initialization, the shell process set itself to ignore job control signals; see Initializing the Shell. As a result, any child processes it creates also ignore these signals by inheritance. This is definitely undesirable, so each child process should explicitly set the actions for these signals back to `SIG_DFL` just after it is forked.

Since shells follow this convention, applications can assume that they inherit the correct handling of these signals from the parent process. But every application has a responsibility not to mess up the handling of stop signals. Applications that disable the normal interpretation of the SUSP character should provide some other mechanism for the user to stop the job. When the user invokes this mechanism, the program should send a `SIGTSTP` signal to the process group of the process, not just to the process itself. See Signaling Another Process.

Finally, each child process should call `exec` in the normal way. This is also the point at which redirection of the standard input and output channels should be handled. See Duplicating Descriptors, for an explanation of how to do this.

Here is the function from the sample shell program that is responsible for launching a program. The function is executed by each child process immediately after it has been forked by the shell, and never returns.

         void
         launch_process (process *p, pid_t pgid,
                         int infile, int outfile, int errfile,
                         int foreground)
         {
           pid_t pid;

           if (shell_is_interactive)
             {
               /* Put the process into the process group and give the process group
                  the terminal, if appropriate.
                  This has to be done both by the shell and in the individual
                  child processes because of potential race conditions.  */
               pid = getpid ();
               if (pgid == 0) pgid = pid;
               setpgid (pid, pgid);
               if (foreground)
                 tcsetpgrp (shell_terminal, pgid);

               /* Set the handling for job control signals back to the default.  */
               signal (SIGINT, SIG_DFL);
               signal (SIGQUIT, SIG_DFL);
               signal (SIGTSTP, SIG_DFL);
               signal (SIGTTIN, SIG_DFL);
               signal (SIGTTOU, SIG_DFL);
               signal (SIGCHLD, SIG_DFL);
             }

           /* Set the standard input/output channels of the new process.  */
           if (infile != STDIN_FILENO)
             {
               dup2 (infile, STDIN_FILENO);
               close (infile);
             }
           if (outfile != STDOUT_FILENO)
             {
               dup2 (outfile, STDOUT_FILENO);
               close (outfile);
             }
           if (errfile != STDERR_FILENO)
             {
               dup2 (errfile, STDERR_FILENO);
               close (errfile);
             }

           /* Exec the new process.  Make sure we exit.  */
           execvp (p->argv[0], p->argv);
           perror ("execvp");
           exit (1);
         }

If the shell is not running interactively, this function does not do anything with process groups or signals. Remember that a shell not performing job control must keep all of its subprocesses in the same process group as the shell itself.

Next, here is the function that actually launches a complete job. After creating the child processes, this function calls some other functions to put the newly created job into the foreground or background; these are discussed in Foreground and Background.

         void
         launch_job (job *j, int foreground)
         {
           process *p;
           pid_t pid;
           int mypipe[2], infile, outfile;

           infile = j->stdin;
           for (p = j->first_process; p; p = p->next)
             {
               /* Set up pipes, if necessary.  */
               if (p->next)
                 {
                   if (pipe (mypipe) < 0)
                     {
                       perror ("pipe");
                       exit (1);
                     }
                   outfile = mypipe[1];
                 }
               else
                 outfile = j->stdout;

               /* Fork the child processes.  */
               pid = fork ();
               if (pid == 0)
                 /* This is the child process.  */
                 launch_process (p, j->pgid, infile,
                                 outfile, j->stderr, foreground);
               else if (pid < 0)
                 {
                   /* The fork failed.  */
                   perror ("fork");
                   exit (1);
                 }
               else
                 {
                   /* This is the parent process.  */
                   p->pid = pid;
                   if (shell_is_interactive)
                     {
                       if (!j->pgid)
                         j->pgid = pid;
                       setpgid (pid, j->pgid);
                     }
                 }

               /* Clean up after pipes.  */
               if (infile != j->stdin)
                 close (infile);
               if (outfile != j->stdout)
                 close (outfile);
               infile = mypipe[0];
             }

           format_job_info (j, "launched");

           if (!shell_is_interactive)
             wait_for_job (j);
           else if (foreground)
             put_job_in_foreground (j, 0);
           else
             put_job_in_background (j, 0);
         }