From:	briansul AT microsoft DOT com (Brian Sullivan)
Subject:	GNU-Win32 BUG - Control-C terminates backgrounded jobs
17 Apr 1998 05:51:03 -0700 :
Sender:	root AT cygnus DOT com
Message-ID:	<C35556591D34D111BB5600805F1961B9064D0EA1.cygnus.gnu-win32@red-msg-47.dns.microsoft.com>
To:	"'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>

The behavior occurs on both Beta 19 and 19.1

The problem:

  Running jobs in the background, such as:

	bash-2.01$ emacs bugreport.txt &
            [1]  1004
            bash-2.01$ jobs
            [1]+  Running                 emacs &
            $ <CNTL>-C
            [1]+  Interrupt               emacs
            bash-2.01$

  Typing Control-C interrupts both the foreground process (if there is one)
as it should,
but it also interrupts all of the backgrounded processes as well, like my
emacs process
above.  This is very disturbing.  Perhaps I am missing something like a
nohup,
but I can't think of what.  Is there a way of protecting the backgrounded
process from
being killed when the interactive bash shell receives a control C.


-
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".

- Raw text -