X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: tty initialization failure under cygwin 1.7.2? Date: Fri, 23 Apr 2010 10:16:08 -0700 Message-ID: From: "Egerton, Jim" To: Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 I ran across this same problem today on Server 2008 with 1.7.3(0.225/5/3) and may have some info to help reproduce this issue. I get this error using: $ cmd /c "bash -c ls" 7 [main] bash 3336 C:\bin\bash.exe: *** fatal error - couldn't initialize fd 0 for /dev/tty2 with an ssh session and a non administrators account. If I use RDP or an administrative account, it works fine. While the example probably seems a bit bizarre, it's actually something you would run into if you used backticks with ActiveState Perl to execute a Cygwin command. jim >On Apr 1 14:31, Eric Berge wrote: >=20 >=20 > I recently updated to 1.7.2 from 1.7.1 with the March 15 development > patch and noticed I was getting some process failures. In particular > I was running the Coverity static analysis tool, and was getting an > error about not being able to "initialize fd 0 for /dev/tty0". >=20 > This problem does not appear to occur with remote desktop, just with > ssh. >=20 > I've been searching around for a simpler version of the problem > and this is what I found: >=20 > The test scenario is to do the following: >=20 > 1. ssh into an cygwin sshd server with an explicit password > 2. Run "cmd" > 3. From "cmd" run "ls" >=20 > I unfortunately no longer have the 1.7.1 + Mar15 patch running but > with cygwin 1.5 and running "ls" lists the entries of the directory > as expected. However, running on 1.7.2 has the following output: >=20 > C:\cygwin\home\eberge>ls > ls > 12 [main] ls 3984 C:\cygwin\bin\ls.exe: *** fatal error - couldn't initialize fd 0 for /dev/tty0 >=20 > C:\cygwin\home\eberge> >=20 > I hope this is reflective of the problem I had with Coverity. It is > the same error message at least. Is this indicative of an underlying > problem in 1.7.2 or is this related to any sort of reconfiguration I > need to do on my box after updating to 1.7.2? I'm wondering if that's a side effect with some other software. I can not reproduce your problem. I tried your test scenario and it works for me. I don't get any weird error from ls. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple