Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-WM-Posted-At: avacado.atomice.net; Wed, 3 Jul 02 01:14:52 +0100 Message-ID: <03e701c22226$a6e25e70$0100a8c0@advent02> From: "Chris January" To: References: <03bb01c22220$8b6030b0$0100a8c0@advent02> <20020703000349.GB8916@redhat.com> Subject: Re: Fw: Problem with signal 21 and multiple bash windows. Date: Wed, 3 Jul 2002 01:14:52 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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. > > Works fine here. Ok - I will try to investigate myself further then. 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/