Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-WM-Posted-At:	avacado.atomice.net; Wed, 3 Jul 02 00:31:09 +0100
Message-ID:	<03bb01c22220$8b6030b0$0100a8c0@advent02>
From:	"Chris January" <chris AT atomice DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	Fw: Problem with signal 21 and multiple bash windows.
Date:	Wed, 3 Jul 2002 00:31:09 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

> With latest CVS cygwin1.dll:
> I click cygwin.bat, and bash opens.
> I click cygwin.bat again and a console window opens, but the bash prompt
> does not appear.
> Further investigation with strace shows that the second instance of bash
is
> getting signal 21 (SIGTTYIN) over and over again.
> If the second instance of bash is launched using cygwin.bat from the
cmd.exe
> command line, the same problem occurs.
> If bash is run as "bash --login -i" from c:\cygwin\bin from the cmd.exe
> command line, the bash prompt appears.
> If SET CYGWIN=tty is typed before running bash directly from the cmd.exe
> command line, the bash prompt does not appear and an strace shows the
signal
> 21 problem.
>
> So it seems that setting the tty flag in the CYGWIN environment variable
> causes the second, third, fourth, etc. instances of bash to go into an
> infinite loop receiving SIGTTYIN.
>
> Regards
> Chris
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -