From: Kevin W. Hammond (hammond@kwhpc.caseng.com)
Date: 08/31/92 

From: Kevin W. Hammond <hammond@kwhpc.caseng.com>
Subject: Re: Background processes not dying on parent exit
Date: Mon, 31 Aug 1992 13:35:21 GMT

|
| In article <1992Aug31.040048.27053@athena.mit.edu> you write:
| |>
| |> I ran a process in the background from tcsh with the ampersand (&). I would
| |> have expected that when I logged out of the shell that my background processes
| |> would have died as well, but they didn't.
| |>
| |> Is the shell responsible for killing the background processes, or, since the
| |> shell is the parent of them and has been terminated, shouldn't the OS kill
| |> the processes automatically?
| |>
|
| This is what is supposed to happen. This allows you to start a long job and
| logout, allowing another person to use the computer while your job is running.
|

I thought that was supposed to happen only if you ran the background job via
nohup. In otherwords, when then parent shell would exit, it would send SIGHUP
to all of it's children, letting them know the parent was exiting. Running
the program nohup would make the child immune to such a signal.

-kwh- 

-- 
Kevin W. Hammond
hammond@kwhpc.caseng.com

  CASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161