Print this page
13507 some man pages need update following 13405
6308 some man pages are obsolete after moving to ksh builtins
@@ -4,29 +4,10 @@
NAME
jobs, fg, bg, stop, notify - control process execution
SYNOPSIS
- sh
- jobs [-p | -l] [% job_id...]
-
-
- jobs -x command [arguments]
-
-
- fg [% job_id...]
-
-
- bg [% job_id...]
-
-
- stop % job_id...
-
-
- stop pid...
-
-
csh
jobs [-l]
fg [% job_id]
@@ -42,26 +23,10 @@
stop pid...
- ksh
- jobs [-lnp] [% job_id...]
-
-
- fg [% job_id...]
-
-
- bg [% job_id...]
-
-
- stop % job_id...
-
-
- stop pid...
-
-
ksh93
jobs [-lnp] [job_id...]
fg [job_id...]
@@ -69,108 +34,10 @@
bg [job_id...]
DESCRIPTION
- sh
- When Job Control is enabled, the Bourne shell built-in jobs reports all
- jobs that are stopped or executing in the background. If %job_id is
- omitted, all jobs that are stopped or running in the background is
- reported. The following options modify or enhance the output of jobs:
-
- -l
- Reports the process group ID and working directory of the jobs.
-
-
- -p
- Reports only the process group ID of the jobs.
-
-
- -x
- Replaces any job_id found in command or arguments with the
- corresponding process group ID, and then executes command passing
- it arguments.
-
-
-
- When the shell is invoked as jsh, Job Control is enabled in addition to
- all of the functionality described previously for sh. Typically Job
- Control is enabled for the interactive shell only. Non-interactive
- shells typically do not benefit from the added functionality of Job
- Control.
-
-
- With Job Control enabled every command or pipeline the user enters at
- the terminal is called a job_id. All jobs exist in one of the following
- states: foreground, background or stopped. These terms are defined as
- follows:
-
- 1. A job in the foreground has read and write access to the
- controlling terminal.
-
- 2. A job in the background is denied read access and has
- conditional write access to the controlling terminal (see
- stty(1))
-
- 3. A stopped job is a job that has been placed in a suspended
- state, usually as a result of a SIGTSTP signal (see
- signal.h(3HEAD)).
-
-
- Every job that the shell starts is assigned a positive integer, called
- a job_id number which is tracked by the shell and are used as an
- identifier to indicate a specific job. Additionally, the shell keeps
- track of the current and previous jobs. The current job is the most
- recent job to be started or restarted. The previous job is the first
- non-current job.
-
-
- The acceptable syntax for a Job Identifier is of the form:
-
-
- %job_id
-
-
- where job_id can be specified in any of the following formats:
-
- % or +
- for the current job
-
-
- -
- for the previous job
-
-
- ?<string>
- specify the job for which the command line uniquely
- contains string.
-
-
- n
- for job number n, where n is a job number
-
-
- pref
- where pref is a unique prefix of the command name (for
- example, if the command ls -l name were running in the
- background, it could be referred to as %ls); pref cannot
- contain blanks unless it is quoted.
-
-
-
- When Job Control is enabled, fg resumes the execution of a stopped job
- in the foreground, also moves an executing background job into the
- foreground. If %job_id is omitted the current job is assumed.
-
-
- When Job Control is enabled, bg resumes the execution of a stopped job
- in the background. If %job_id is omitted the current job is assumed.
-
-
- stop stops the execution of a background job(s) by using its job_id, or
- of any process by using its pid; see ps(1).
-
csh
The C shell built-in, jobs, without an argument, lists the active jobs
under job control.
-l
@@ -241,135 +108,10 @@
notify notifies the user asynchronously when the status of the current
job or specified jobs changes.
- ksh
- jobs displays the status of the jobs that were started in the current
- shell environment. When jobs reports the termination status of a job,
- the shell removes its process ID from the list of those known in the
- current shell execution environment.
-
-
- job_id specifies the jobs for which the status is to be displayed. If
- no job_id is specified, the status information for all jobs are
- displayed.
-
-
- The following options modify or enhance the output of jobs:
-
- -l
- (The letter ell.) Provides more information about each job
- listed. This information includes the job number, current job,
- process group ID, state and the command that formed the job.
-
-
- -n
- Displays only jobs that have stopped or exited since last
- notified.
-
-
- -p
- Displays only the process IDs for the process group leaders of
- the selected jobs.
-
-
-
- By default, jobs displays the status of all the stopped jobs, running
- background jobs, and all jobs whose status has changed and have not
- been reported by the shell.
-
-
- If the monitor option of the set command is turned on, an interactive
- shell associates a job with each pipeline. It keeps a table of current
- jobs, printed by the jobs command, and assigns them small integer
- numbers. When a job is started asynchronously with &, the shell prints
- a line which looks like:
-
-
- [1] 1234
-
-
- indicating that the job, which was started asynchronously, was job
- number 1 and had one (top-level) process, whose process id was 1234.
-
-
- If you are running a job and wish to do something else you can hit the
- key ^Z (Control-Z) which sends a STOP signal to the current job. The
- shell then normally indicates that the job has been "Stopped" (see
- OUTPUT below), and print another prompt. You can then manipulate the
- state of this job, putting it in the background with the bg command, or
- run some other commands and then eventually bring the job back into the
- foreground with the foreground command fg. A ^Z takes effect
- immediately and is like an interrupt, in that pending output and unread
- input are discarded when it is typed.
-
-
- There are several ways to refer to jobs in the shell. A job can be
- referred to by the process id of any process of the job or by one of
- the following:
-
- %number
- The job with the specified number.
-
-
- %string
- Any job whose command line begins with string; works only
- in the interactive mode when the history file is active.
-
-
- %?string
- Any job whose command line contains string; works only in
- the interactive mode when the history file is active.
-
-
- %%
- Current job.
-
-
- %+
- Equivalent to %%.
-
-
- %-
- Previous job.
-
-
-
- The shell learns immediately whenever a process changes state. It
- normally informs you whenever a job becomes blocked so that no further
- progress is possible, but only just before it prints a prompt. This is
- done so that it does not otherwise disturb your work. When the monitor
- mode is on, each background job that completes triggers any trap set
- for CHLD. When you try to leave the shell while jobs are running or
- stopped, you are warned that `You have stopped (running) jobs.' You can
- use the jobs command to see what they are. If you do this or
- immediately try to exit again, the shell does not warn you a second
- time, and the stopped jobs are terminated.
-
-
- fg moves a background job from the current environment into the
- foreground. Using fg to place a job in the foreground removes its
- process ID from the list of those known in the current shell execution
- environment. The fg command is available only on systems that support
- job control. If job_id is not specified, the current job is brought
- into the foreground.
-
-
- bg resumes suspended jobs from the current environment by running them
- as background jobs. If the job specified by job_id is already a running
- background job, bg has no effect and exits successfully. Using bg to
- place a job into the background causes its process ID to become `known
- in the current shell execution environment, as if it had been started
- as an asynchronous list. The bg command is available only on systems
- that support job control. If job_id is not specified, the current job
- is placed in the background.
-
-
- stop stops the execution of a background job(s) by using its job_id, or
- of any process by using its pid. See ps(1).
-
ksh93
jobs displays information about specified jobs that were started by the
current shell environment on standard output. The information contains
the job number enclosed in [...], the status, and the command line that
started the job.
@@ -548,11 +290,11 @@
See environ(5) for descriptions of the following environment variables
that affect the execution of jobs, fg, and bg: LANG, LC_ALL, LC_CTYPE,
LC_MESSAGES, and NLSPATH.
EXIT STATUS
- sh, csh, ksh
+ csh
The following exit values are returned for jobs, fg, and bg:
0
Successful completion.
@@ -597,14 +339,12 @@
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
- csh, sh, ksh
+ csh
-
-
+--------------------+-------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------+-------------------+
|Interface Stability | Committed |
+--------------------+-------------------+
@@ -611,21 +351,18 @@
|Standard | See standards(5). |
+--------------------+-------------------+
ksh93
-
-
+--------------------+-----------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------+-----------------+
|Interface Stability | Uncommitted |
+--------------------+-----------------+
SEE ALSO
- csh(1), kill(1), ksh(1), ksh93(1), ps(1), sh(1), stop(1),
- shell_builtins(1), stty(1), wait(1), signal.h(3HEAD), attributes(5),
- environ(5), standards(5)
+ csh(1), kill(1), ksh93(1), ps(1), stop(1), shell_builtins(1), stty(1),
+ wait(1), signal.h(3HEAD), attributes(5), environ(5), standards(5)
- November 2, 2007 JOBS(1)
+ February 9, 2021 JOBS(1)