Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<3.0.5.32.19990614133654.00b2dd50@nats13.informatik.uni-hamburg.de>
X-Sender:	herron AT nats13 DOT informatik DOT uni-hamburg DOT de
X-Mailer:	QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date:	Mon, 14 Jun 1999 13:36:54 +0200
To:	cygwin AT sourceware DOT cygnus DOT com
From:	Dan Herron <herron AT informatik DOT uni-hamburg DOT de>
Subject:	Re: Ctrl-c in bash causes background processes to exit
In-Reply-To:	<002b01bea34b$4a88b320$b6ac51d1@ekwqq>
Mime-Version:	1.0

At 01:32 AM 5/21/99 -0400, Kevin Low wrote: 
> I am using bash from cygwin b20. How do I prevent all background 
> jobs from exiting whenever I press ctrl-c in bash? For example, if
> I run telnet in the background, pressing ctrl-c will kill telnet.

You need to set "tty" in your CYGWIN environment variable. E.g.,

export CYGWIN="tty" (or set it in the "system"--> environment control-panel.)

Somebody told me this a while ago, but pointed out that this screws up
lots of programs that use the console IO. And, indeed, it made all sorts
of things go wrong for me, although I can't actually recall *what* at
this point.

Actually, can somebody explain what it is that TTY does? And why it
causes problems both to have it and to not have it? And is there a list
of all the CYGWIN options somewhere, with a description of what each one does?

Dan


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -