Reese Knowledgebase

Job Control in Unix

View Kristian Reese's profile on LinkedIn

If you like this article, please +1 or Recommend via FB with the provided buttons above:

Article ID: 26
by: Reese K.
Posted: 27 Jan, 2012
Last updated: 27 Jan, 2012
Views: 1069

Useful Commands--Summary

    control-z Stop (don't kill) the foreground job, and then return to the shell
    jobs Check the status of jobs in the current session
    ps -u username Check the status of processes, including those from other sessions. On BSD systems, use 'ps -gx'.
    kill -9 %1 Kill a job, by specifying its job number after the percent sign
    kill -9 123 Kill a process, by specifying its process id (PID) number
    bg Run the most recently stopped job in the background
    fg Bring most recently backgrounded job to the foreground
    fg %1 Bring a job to foreground by specifying its job number after the percent sign

Foreground vs. Background

A foreground job can receive keyboard input and signals such as Control-C from the controlling terminal, background jobs cannot. If the login session is disconnected, foreground jobs are terminated by a hang-up signal, while backgrounds jobs are not. Both foreground and background jobs can write to the controlling terminal.

Putting a Job in the Background

Jobs can be put in the background either by initiating them in the background or by stopping a foreground job and then specifying that it be continued in the background.

The way a job is initiated in the background is by putting an ampersand (&) at the end of the command line. For example, to start the excellent web browser Mozilla, if you plan on using the terminal for other activities while the web browser is running, you can type:

	mozilla &


A second technique is to stop the foreground job with control-Z, and then to specify that the job be continued in the background with the "bg" command (The Carrot, ^, represents holding down the control key while you press the letter after it). So, if you start Mozilla


When you run in the background a program that uses a graphical user interface for interaction, you will still be able to interact with its graphical elements in your windowing system. If you suspend it with ^Z, you will not be able to interact with it until you start it running, either in the foreground (fg) or the background (bg).

Monitoring Background Jobs

The commands "jobs" and "ps" can be used to monitor the status of background jobs. As a demonstration, suppose that

  1. A large compilation job is running in the background
  2. Mozilla is started, and then stopped with ^Z

The report from the command "jobs -l" would look something like this:

[1]  - 12527 Running              make oberon
	[2]  + 12530 Stopped              mozilla

The "[ ]" numbers are the job numbers that "bg" (background), "fg" (foreground), and "kill" use. (See the sections below for the details).

The report from the command "ps -u username" would look something like this:

	10272 pts/10   3:40 mozilla-
	9418 pts/10   0:00 csh
	10198 pts/10   0:00 run-mozi
	12527 pts/10   2:07 make oberon


The information in this display is explained in greater detail in "man  ps". It shows the running processes in greater detail than the "jobs" output. The numbers in the PID column are the process identification numbers associated with the processes named in the COMMAND column, and can be used by the "kill" command (see below).

Bringing a Background Job to the Foreground

A background job may be brought to the foreground if it was initiated during the current login session. Jobs which were initiated during other login sessions and which are still running cannot be brought to the foreground. However, it is possible to send signals to such jobs using the "kill" command-- see below. A background job or a stopped job may be brought to the foreground with the command fg.

	fg  %1

The number following the percent sign is obtained from the leftmost column of the table given by the "jobs" command. See the discussion above, "Monitoring Background Jobs".

Terminating Background Jobs

Jobs from the current session can usually be terminated by bringing them to the foreground and interrupting them with control-c key.

Another technique for terminating jobs running under your user id employs the "kill" command. There are two ways to refer to a particular job. The first uses the number in the leftmost column of the jobs command, as follows:

	kill -9 %1

The second way uses the process id given in the leftmost column of the "ps -gx" command, as follows:

	kill -9  pid-number

This can be used to terminate stopped and background jobs from the current session. It can be used to terminate jobs initiated by other login sessions of your user id.

Impact on System Performance

The effect of background jobs on system performance depends upon the priority at which they run and how much RAM they require to run. Large jobs can consume immense amounts of RAM which can severely limit system performance. If the program requires too much RAM, the CPU will be wasting a lot of time swapping memory to and from disk rather than executing the jobs it needs to.

The other variable which affects system performance is job priority. If your jobs run at low priority, they will be done at the system's leisure and system performance will not be affected. If they are run at normal priority, they will increase the competition for resources and performance may be degraded. On a heavily loaded system, jobs should only be put into the background at low priority, using the "nice" command. To "nice" a job, just put the word "nice" before the command as you would regularly give it.

The current load on the system may be determined with:


The three numbers at the right of the resulting report indicate the load. If the first of the three is over 3, background jobs should only be initiated with low priority (niced). For example:

	nice make oberon

To change the priority of a running job, use the command "renice". For example, if the command 'make oberon' with process ID 12527 is slowing things down too much for everyone else, you could use the command;

	renice 19 12527

This article was:   Helpful | Not Helpful
External links

Prev   Next
Redirecting standard output and standard error     Display top 10 processes eating up CPU