From: chet AT nike DOT ins DOT cwru DOT edu (Chet Ramey)
Subject: Re: bash and '&'
8 Apr 1998 21:28:36 -0700
Message-ID: <980407193138.AA27994.SM.cygnus.gnu-win32@nike.ins.cwru.edu>
References: <19980331141913 DOT 15879 DOT qmail AT hotmail DOT com>
Reply-To: chet AT po DOT cwru DOT edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: earnie_boyd AT hotmail DOT com
Cc: gnu-win32 AT cygnus DOT com, wku1 AT utk DOT edu

> This is taken from the bash.info file:
> ---from bash.info---
> The shell exits by default upon receipt of a `SIGHUP'.  Before exiting, 
> it resends the `SIGHUP' to all jobs, running or stopped.  To
> prevent the shell from sending the `SIGHUP' signal to a particular job, 
> remove it from the jobs table with the `disown' builtin (*note Job 
> Control Builtins::.) or use `disown -h' to mark it to not receive
> `SIGHUP'.
> ---end bash.info---
> 
> I could find no switches to force this to happen automatically.  Perhaps 
> the AIX bash you used was modified to allow this to happen.

The other half of that is that if bash does *not* exit as the result
of a SIGHUP, such as an EOF on stdin or via the `exit' builtin, it
does not send SIGHUP to any jobs at all.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, Case Western Reserve University	Internet: chet AT po DOT CWRU DOT Edu
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".