This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: bash and '&'
- To: earnie_boyd at hotmail dot com
- Subject: Re: bash and '&'
- From: Chet Ramey <chet at nike dot ins dot cwru dot edu>
- Date: Tue, 7 Apr 1998 15:31:38 -0400
- Cc: gnu-win32 at cygnus dot com, wku1 at utk dot edu
- Read-Receipt-To: chet@po.CWRU.Edu
- Reply-To: chet at po dot cwru 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@po.CWRU.Edu
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".