Lines Matching refs:processes
23 parent process to abort a child, or two related processes to communicate
118 An external event generally has to do with I/O or other processes.
527 termination effectively disconnects all processes in the session from
621 processes terminates or stops.
624 handler for this signal while there are child processes that have
627 applies to those processes or not depends on the particular operating
679 read from the terminal, all of the processes in the job are sent a
716 orphaned processes lying around the system.
811 to all the processes in the foreground process group of the controlling
1494 @r{- kill child processes}
1637 where the system is busy running some other processes while the signals
1645 child processes that generate them. It assumes that the program keeps track
1646 of all the child processes with a chain of structures as follows:
1700 @r{stopped or terminated child processes, so return.} */
1724 /* @r{Loop around to handle all the processes}
2229 might want to send signals between processes are:
2239 the other processes in the group when an error or other event occurs.
2242 Two processes need to synchronize while working together.
2245 This section assumes that you know a little bit about how processes
2273 All processes in the same process group as the sender.
2279 If the process is privileged, send the signal to all processes except
2280 for some special system processes. Otherwise, send the signal to all
2281 processes with the same effective user ID.
2293 returned. If @var{pid} specifies sending a signal to several processes,
2295 There's no way you can tell which of the processes got the signal
2306 the processes in the process group named by @var{pid}.
2345 behavior such as arbitrarily killing off processes belonging to another
2347 parent, child, and sibling processes, and in these situations you
2354 is determined by the user IDs of the two processes. This concept is
2571 Note that you must not use @code{sigprocmask} in multi-threaded processes,