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
Date: Tue, 2 Jul 2002 20:20:24 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Fw: Problem with signal 21 and multiple bash windows.
Message-ID: <20020703002024.GC8916@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <03bb01c22220$8b6030b0$0100a8c0 AT advent02> <20020703000349 DOT GB8916 AT redhat DOT com> <03e701c22226$a6e25e70$0100a8c0 AT advent02>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <03e701c22226$a6e25e70$0100a8c0@advent02>
User-Agent: Mutt/1.3.23.1i

On Wed, Jul 03, 2002 at 01:14:52AM +0100, Chris January wrote:
>> >> 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.
>>
>> Works fine here.
>Ok - I will try to investigate myself further then.

I meant to ask: Could you post a summary of your configuration?  OS, number of
CPUs, amount of memory?  You indicated that this happens with just CYGWIN=tty,
right?  No need to set ntsec or anything else?

cgf

--
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/