Difference between revisions of "Job control"

Latest revision as of 04:42, 21 April 2023

When using Linux via a terminal, a user will initially only have a single process running, their login shell. Most tasks (directory listing, editing files, etc.) can easily be accomplished by letting the program take control of the terminal and returning control to the shell when the program exits; however, sometimes the user will wish to carry out a lengthy task in the background while using the terminal for another purpose. Job control is a facility developed to make this possible, by allowing the user to start programs in the background, send programs into the background, bring background programs into the foreground, and start and stop running programs. Programs under the influence of a job control facility are referred to as jobs.

Implementation

• Typically, the shell keeps a list of jobs in a job table. A job consists of all the members of a pipeline.
• A program can be started as a background task by appending &^[1] to the command line; its output is directed to the terminal (potentially interleaved with other programs' output) but it cannot read from the terminal input.
• A task running in the foreground can be stopped by typing the suspend character (Ctrl+Z); this sends SIGTSTP to the process and returns control to the shell.
• The process can be resumed as a background job with the bg builtin or as the foreground job with fg; in either case the shell redirects I/O appropriately and sends SIGCONT to the process.
• jobs will list the background jobs existing in the job table, along with their job number and job state (stopped or running).
• The kill builtin (not /bin/kill) can signal processes by job number as well as by process ID.
• disown can be used to remove jobs from the job table, converting them from jobs into daemons so that they continue executing when the user logs out.

Job control basics

Job control refers to the ability to selectively stop (suspend) the execution of processes and continue (resume) their execution at a later point. A user typically employs this facility via an interactive interface supplied jointly by the system's terminal driver and Bash.

The shell associates a job with each pipeline. It keeps a table of currently executing jobs, which may be listed with the jobs command. When Bash starts a job asynchronously, it prints a line that looks like:

[1] 25647

indicating that this job is job number 1 and that the process ID of the last process in the pipeline associated with this job is 25647. All of the processes in a single pipeline are members of the same job. Bash uses the job abstraction as the basis for job control.

To facilitate the implementation of the user interface to job control, the operating system maintains the notion of a current terminal process group ID. Members of this process group (processes whose process group ID is equal to the current terminal process group ID) receive keyboard-generated signals such as SIGINT. These processes are said to be in the foreground. Background processes are those whose process group ID differs from the terminal's; such processes are immune to keyboard-generated signals. Only foreground processes are allowed to read from or write to the terminal. Background processes which attempt to read from (write to) the terminal are sent a SIGTTIN (SIGTTOU) signal by the terminal driver, which, unless caught, suspends the process.

If the operating system on which Bash is running supports job control, Bash contains facilities to use it. Typing the suspend character (typically '^Z', Control-Z) while a process is running causes that process to be stopped and returns control to Bash. Typing the delayed suspend character (typically '^Y', Control-Y) causes the process to be stopped when it attempts to read input from the terminal, and control to be returned to Bash. The user then manipulates the state of this job, using the bg command to continue it in the background, the fg command to continue it in the foreground, or the kill command to kill it. A '^Z' takes effect immediately, and has the additional side effect of causing pending output and typeahead to be discarded.

There are a number of ways to refer to a job in the shell. The character '%' introduces a job name.

Job number n may be referred to as '%n'. The symbols '%%' and '%+' refer to the shell's notion of the current job, which is the last job stopped while it was in the foreground or started in the background. The previous job may be referenced using '%-'. In output pertaining to jobs (eg, the output of the jobs command), the current job is always flagged with a '+', and the previous job with a '-'.

A job may also be referred to using a prefix of the name used to start it, or using a substring that appears in its command line. For example, '%ce' refers to a stopped ce job. Using '%?ce', on the other hand, refers to any job containing the string 'ce' in its command line. If the prefix or substring matches more than one job, Bash reports an error.

Simply naming a job can be used to bring it into the foreground: '%1' is a synonym for 'fg %1', bringing job 1 from the background into the foreground. Similarly, '%1 &' resumes job 1 in the background, equivalent to 'bg %1'.

The shell learns immediately whenever a job changes state. Normally, Bash waits until it is about to print a prompt before reporting changes in a job's status so as to not interrupt any other output. If the '-b' option to the set builtin is enabled, Bash reports such changes immediately (see: "The Set Builtin"). Any trap on SIGCHLD is executed for each child process that exits.

If an attempt to exit Bash is while jobs are stopped, the shell prints a message warning that there are stopped jobs. The jobs command may then be used to inspect their status. If a second attempt to exit is made without an intervening command, Bash does not print another warning, and the stopped jobs are terminated.

Job control builtins

• bg

bg [jobspec]

Resume the suspended job jobspec in the background, as if it had been started with '&'. If jobspec is not supplied, the current job is used. The return status is zero unless it is run when job control is not enabled, or, when run with job control enabled, if jobspec was not found or jobspec specifies a job that was started without job control.

• fg

fg [jobspec]

Resume the job jobspec in the foreground and make it the current job. If jobspec is not supplied, the current job is used. The return status is that of the command placed into the foreground, or non-zero if run when job control is disabled or, when run with job control enabled, jobspec does not specify a valid job or jobspec specifies a job that was started without job control.

• jobs

jobs [-lnprs] [jobspec]

jobs -x command [arguments]

The first form lists the active jobs. The options have the following meanings:

-l

List process IDs in addition to the normal information.

-n

Display information only about jobs that have changed status since the user was last notified of their status.

-p

List only the process ID of the job's process group leader.

-r

Restrict output to running jobs.

-s

Restrict output to stopped jobs.

If jobspec is given, output is restricted to information about that job. If jobspec is not supplied, the status of all jobs is listed.

If the '-x' option is supplied, jobs replaces any jobspec found in command or arguments with the corresponding process group ID, and executes command, passing it arguments, returning its exit status.

• kill

kill [-s sigspec] [-n signum] [-sigspec] jobspec or pid

kill -l [exit_status]

Send a signal specified by sigspec or signum to the process named by job specification jobspec or process ID pid. sigspec is either a signal name such as SIGINT (with or without the SIG prefix) or a signal number; signum is a signal number. If sigspec and signum are not present, SIGTERM is used. The '-l' option lists the signal names. If any arguments are supplied when '-l' is given, the names of the signals corresponding to the arguments are listed, and the return status is zero. exit_status is a number specifying a signal number or the exit status of a process terminated by a signal. The return status is zero if at least one signal was successfully sent, or non-zero if an error occurs or an invalid option is encountered.

• wait

wait [jobspec or pid]

Wait until the child process specified by process ID pid or job specification jobspec exits and return the exit status of the last command waited for. If a jobspec is given, all processes in the job are waited for. If no arguments are given, all currently active child processes are waited for, and the return status is zero. If neither jobspec nor pid specifies an active child process of the shell, the return status is 127.

• disown

disown [-ar] [-h] [jobspec ...]

Without options, each jobspec is removed from the table of active jobs. If the '-h' option is given, the job is not removed from the table, but is marked so that SIGHUP is not sent to the job if the shell receives a SIGHUP. If jobspec is not present, and neither the '-a' nor '-r' option is supplied, the current job is used. If no jobspec is supplied, the '-a' option means to remove or mark all jobs; the '-r' option without a jobspec argument restricts operation to running jobs.

• suspend

suspend [-f]

Suspend the execution of this shell until it receives a SIGCONT signal. The '-f' option means to suspend even if the shell is a login shell.

• set

(see: Bash Reference Manual)

When job control is not active, the kill and wait builtins do not accept jobspec arguments. They must be supplied process IDs.

Job control variables

auto_resume 

This variable controls how the shell interacts with the user and job control. If this variable exists then single word simple commands without redirections are treated as candidates for resumption of an existing job. There is no ambiguity allowed; if there is more than one job beginning with the string typed, then the most recently accessed job will be selected. The name of a stopped job, in this context, is the command line used to start it. If this variable is set to the value 'exact', the string supplied must match the name of a stopped job exactly; if set to 'substring', the string supplied needs to match a substring of the name of a stopped job. The 'substring' value provides functionality analogous to the '%?' job ID (see Job Control Basics). If set to any other value, the supplied string must be a prefix of a stopped job's name; this provides functionality analogous to the '%' job ID.

Process state codes

Note: See man ps for complete list; under "PROCESS STATE CODES" section.

R 

runnable

S 

stopped (usually because it is waiting on input or doing something else that does not require processing time from the CPU)

D 

uninterruptible IO wait (usually requires a reboot to clear)

T 

process is stopped (send a SIGCONT to start the process again)

Z 

process is defunct (either kill the parent or reboot)

Signals

Note: Look in /usr/include/asm/signal.h for a complete list of signals, or execute kill -l.

• 2 SIGBUS — Bus Error
• 9 SIGKILL — Terminate a process. Noninterruptible.
• 11 SIGSEGV — Segmentation Fault.
• 15 SIGTERM — Terminate a process in an orderly fashion.
• 17 SIGCHLD — Child process terminated
• 18 SIGCONT — Continue executing after a stop
• 19 SIGSTOP — Stop executing

See also

• nohup
• ps

References and notes

1. ↑ This section uses Bash syntax; other shells offer similar functionality under other names.

External links

• Job control in Bash