Lines Matching full:job

582 .I job
585 Usually, every line typed to the shell creates a job.
594 at the end of the commands, then the job is started as a
597 immediately prompts and is ready for another command.  The job runs
619 telling you that the job has completed.
633 How do you know when a background job is finished?
640 If the job did not terminate normally the `Done' message might say
656 of all commands in the job as well as the working directory where the job was
658 Each job in the table is either running
664 Only one job can be running in the foreground at one time, but several
665 jobs can be suspended or running in the background at once.  As each job
668 .I "job number"
669 which can be used later to refer to the job in the commands described below.
671 the same until the job terminates and then are re-used.
673 When a job is started in the background using `&', its number, as well
686 together as a background job.  After starting the job, the shell prints
687 the job number in brackets (2 in this case) followed by the process number
688 of each program started in the job.  Then the shell immediates prompts for
689 a new command, leaving the job running simultaneously.
695 foreground job.  A background job can become suspended by using the
699 or the background.  The shell notices when a job becomes stopped and
725 the suspended job.  Also, foreground jobs can be suspended and then
729 stop waiting for the foreground job to finish.  Thus
741 when a foreground job ends up taking longer than you expected and you
745 .I "job control"
748 All job name arguments begin with the character `%', since some of the
752 The default job (when no argument is given) is called the
757 When only one job is stopped or running in the background (the usual case)
758 it is always the current job thus no argument is needed.
759 If a job is stopped while running in the foreground it becomes the
761 job and the existing current job becomes the
765 When the current job terminates, the previous job becomes the current job.
767 the previous job); `%#', where # is the job number;
774 command types the table of jobs, giving the job number,
776 suspended job.  With the `\-l' option the process numbers are also
799 command runs a suspended or background job in the foreground.  It is
800 used to restart a previously suspended job or change a background job
804 to change the `ls' job from the
809 command runs a suspended job in the background.  It is usually used
810 after stopping the currently running foreground job with the
813 command changes a foreground job into a background job.
816 command suspends a background job.
820 command terminates a background or suspended job immediately.
838 of a specific job should be
841 If a job running in the background tries to read input from the terminal
842 it is automatically stopped.  When such a job is then run in the
843 foreground, input can be given to the job.  If desired, the job can
868 So after the `s' command was issued, the `ed' job was stopped with ^Z
876 command returned the `ed' job to the foreground where it could once again
886 jobs from interrupting foreground job output and allows you to run
887 a job in the background without losing terminal output.  It also
925 it would be very unpleasant to have a background job change the state
1072 Since the shell remembers the working directory in which each job
1074 a job in the foreground which has a different working directory than the
1077 background job to run in the foreground, the shell warns you that the
1078 working directory of the currently running foreground job is different
1099 issued.  In the above example the `ed' job was still in `/mnt/bill/project'
1101 A similar warning is given when such a foreground job
1114 directory a job is started in, and assumes it stays there.