X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_YG,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <229052.11309.qm@web55108.mail.re4.yahoo.com>
References: <F3F5304BB3DD2445AF37A9E799FF6EE10DA64068 AT CAVS1 DOT sanmateo DOT corp DOT akamai DOT com>
Date: Fri, 23 Apr 2010 11:10:03 -0700 (PDT)
From: Eric Berge <emberge AT yahoo DOT com>
Subject: Re: tty initialization failure under cygwin 1.7.2?
To: cygwin AT cygwin DOT com
In-Reply-To: <F3F5304BB3DD2445AF37A9E799FF6EE10DA64068@CAVS1.sanmateo.corp.akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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



Followups to the original message demonstrated that this was
a problem when running in a non-Administrator account.  That's
still a bug, but does provide a workaround until this is fixed.

I've been monitoring the updates as they've been coming in and
have not seen a fix in 1.7.5.  It did sound like the fix was
not trivial so I'm not aware of an ETA for this.

Interestingly enough, I just ran cygcheck -s to verify the
latest version for this email, and cygcheck -s also prints
this error (from cygrunsrv).

Eric



----- Original Message ----
> From: "Egerton, Jim" <jegerton AT akamai DOT com>
> To: cygwin AT cygwin DOT com
> Sent: Fri, April 23, 2010 12:16:08 PM
> Subject: Re: tty initialization failure under cygwin 1.7.2?
> 
> 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:
> 
> 
> 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".
> 
> This problem does not appear to occur with 
> remote desktop, just with
> ssh.
> 
> I've been searching 
> around for a simpler version of the problem
> and this is what I 
> found:
> 
> The test scenario is to do the following:
> 
> 
> 1. ssh into an cygwin sshd server with an explicit password
> 2. 
> Run "cmd"
> 3. From "cmd" run "ls"
> 
> 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:
> 
> 
> 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
> 
> C:\cygwin\home\eberge>
> 
> 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

-- 
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:        
> href="http://cygwin.com/docs.html" target=_blank 
> >http://cygwin.com/docs.html
Unsubscribe info:      
> href="http://cygwin.com/ml/#unsubscribe-simple" target=_blank 
> >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