FG(1) General Commands Manual FG(1)

fg — run jobs in the foreground

fg [job_id]

If job control is enabled (see the description of set -m ), the fg utility will move a background job from the current environment (see Shell Execution Environment ) into the foreground.

Using fg to place a job into the foreground will remove its process ID from the list of those "known in the current shell execution environment"; see chap2(1).

None.

The following operand is supported:

job_id
Specify the job to be run as a foreground job. If no job_id operand is given, the job_id for the job that was most recently suspended, placed in the background or run as a background job will be used. The format of job_id is described in the entry for job control job ID in the XBD specification, .

Not used.

None.

The following environment variables affect the execution of fg :

Provide a default value for the internationalisation variables that are unset or null. If LANG is unset or null, the corresponding value from the implementation-dependent default locale will be used. If any of the internationalisation variables contains an invalid setting, the utility will behave as if none of the variables had been defined.
If set to a non-empty string value, override the values of all the other internationalisation variables.
Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single- as opposed to multi-byte characters in arguments).
Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
Determine the location of message catalogues for the processing of LC_MESSAGES .

Default.

The fg utility writes the command line of the job to standard output in the following format:

"%s\n", <command>

Used only for diagnostic messages.

None.

None.

The following exit values are returned:

Successful completion.
An error occurred.

If job control is disabled, the fg utility will exit with an error and no job will be placed in the foreground.

The fg utility will not work as expected when it is operating in its own utility execution environment because that environment will have no applicable jobs to manipulate. See the APPLICATION USAGE section for bg(1) . For this reason, fg is generally implemented as a shell regular built-in.

None.

None.

bg(1) , kill(1) , jobs(1) , wait(1) .

February 1997 posix.fail