diff options
author | Roland McGrath <roland@gnu.org> | 1994-10-16 23:55:59 +0000 |
---|---|---|
committer | Roland McGrath <roland@gnu.org> | 1994-10-16 23:55:59 +0000 |
commit | 492c48c77c972f2e884442d2945742edf1e8f719 (patch) | |
tree | 85473ebc3331d0d398c8c8cfb5db1ab44900454e /manual | |
parent | ab4ae7a9c1aa86b5adfca14715b7c580b3aae46a (diff) |
(Job Control Signals): In GNU, orphans getting stop sigs get SIGKILL.
Diffstat (limited to 'manual')
-rw-r--r-- | manual/signal.texi | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/manual/signal.texi b/manual/signal.texi index af2a6301a6..7339e4c2cd 100644 --- a/manual/signal.texi +++ b/manual/signal.texi @@ -708,10 +708,13 @@ signals for a process are discarded when it receives a stop signal. When a process in an orphaned process group (@pxref{Orphaned Process Groups}) receives a @code{SIGTSTP}, @code{SIGTTIN}, or @code{SIGTTOU} signal and does not handle it, the process does not stop. Stopping the -process would be unreasonable since there would be no way to continue -it. What happens instead depends on the operating system you are -using. Some systems may do nothing; others may deliver another signal -instead, such as @code{SIGKILL} or @code{SIGHUP}. +process would probably not be very useful, since there is no shell +program that will notice it stop and allow the user to continue it. +What happens instead depends on the operating system you are using. +Some systems may do nothing; others may deliver another signal instead, +such as @code{SIGKILL} or @code{SIGHUP}. In the GNU system, the process +dies with @code{SIGKILL}; this avoids the problem of many stopped, +orphaned processes lying around the system. @ignore On the GNU system, it is possible to reattach to the orphaned process |