« Return to Thread: Pseudo-terminal will not be allocated because stdin is not a terminal.

Re: Pseudo-terminal will not be allocated because stdin is not a terminal.

by peter360 :: Rate this Message:

Reply to Author | View in Thread

Indeed!  It turns out I was using c:\WINDOWS\System32\ssh.exe, which I have no idea how it got there...  I installed openssh and the problem was fixed.  Thanks!

Just out of curiosity, how does a program check if stdin is a "terminal"?  My xterm looks like a terminal to me but apparently the windows version of ssh.exe couldn't figure that out...

Peter

Christopher Faylor-8 wrote:
On Thu, Feb 01, 2007 at 12:10:35PM -0800, peter360 wrote:
>I just installed cygwin/X.    My system is:
>
>$ uname -a
>CYGWIN_NT-5.1 AGAINSTSTONE-LX 1.5.24(0.156/4/2) 2007-01-31 10:57 i686 Cygwin
>
>
>I start the X server using the included startxwin.bat file.  In the xterm
>window this is what I got
>$ ssh destination.host
>Pseudo-terminal will not be allocated because stdin is not a terminal.
>...
>
>ssh asks me for password but as I type the password echoes into the terminal
>window!  I assume this is related to the warning message about not being
>able to allocate Pseudo terminal.  But why?  Why is my stdin not a terminal?
>Anybody has a clue?

Yep.  You have a non-cygwin tool in there somewhere (ssh, maybe?) which doesn't
understand cygwin's ptys.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

 « Return to Thread: Pseudo-terminal will not be allocated because stdin is not a terminal.