Lines Matching refs:processes

32 * Access to the Terminal::      How processes share the controlling terminal.
43 commands from the user's terminal and create processes to execute the
49 several processes.  If you use the @samp{|} operator in a shell command,
50 you explicitly request several programs in their own processes.  But
51 even if you run just one program, it can use multiple processes
53 -c foo.c} typically uses four processes (though normally only two at any
55 in separate processes.
57 The processes belonging to a single command are called a @dfn{process
60 terminate all the processes in the foreground process group.
63 A @dfn{session} is a larger group of processes.  Normally all the
64 processes that stem from a single login belong to the same session.
115 processes created with @code{fork} inherit the controlling terminal from
116 their parent process.  In this way, all the processes in a session
141 unrestricted access to that terminal; background processes do not.  This
148 This normally causes all of the processes in that group to stop (unless
177 in on the terminal.)  This could cause a problem if any processes from
184 When a process group becomes an orphan, its processes are sent a
185 @code{SIGHUP} signal.  Ordinarily, this causes the processes to
270 /* @r{A job is a pipeline of processes.}  */
275   process *first_process;     /* @r{list of processes in this job} */
306 /* @r{Return true if all processes in the job have stopped or completed.}  */
320 /* @r{Return true if all processes in the job have completed.}  */
371 control.  It must leave all processes it creates in the same process
373 child processes to be treated as a single job by the parent shell.  This
445 To create the processes in a process group, you use the same @code{fork}
447 Since there are multiple child processes involved, though, things are a
452 relationships among the processes.  You can either make all the
453 processes in the process group be children of the shell process, or you
454 can make one process in group be the ancestor of all the other processes
467 processes into the new process group.  This is because there is a
470 having all the child processes in the group before it continues
471 executing.  If both the child processes and the shell call
478 as by each of its child processes, to avoid race conditions.
485 processes it creates also ignore these signals by inheritance.  This is
520          @r{child processes because of potential race conditions.}  */
566 After creating the child processes, this function calls some other
594       /* @r{Fork the child processes.}  */
648 shell should wait for processes in that process group to terminate or
652 When all of the processes in the group have either completed or stopped,
656 are sent to the process group, normally all the processes in the job
735 the processes in that job have either terminated or stopped.  It can do
738 for processes that stop as well as processes that terminate.
801     /* @r{No processes ready to report.}  */
812 /* @r{Check for processes that have status information available,}
828 /* @r{Check for processes that have status information available,}
829    @r{blocking until all processes in the given job have reported.}  */
864   /* @r{Update status information for child processes.}  */
872       /* @r{If all processes have completed, tell the user the job has}
1072 are initially no other processes in the new process group, and no other
1210 existing process group.  This can happen if all of the processes in the
1242 normally all processes in the process group are sent a @code{SIGTTOU}