Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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; Tue, 2 Jul 02 21:05:14 +0100 Message-ID: <018f01c22203$c7310500$0100a8c0@advent02> From: "Chris January" To: Subject: Problem with signal 21 and multiple bash windows. Date: Tue, 2 Jul 2002 21:05:14 +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. 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/