I have tried ssh using both interactive and command line mode, and I get the same results. That is - sorry for being pedantic about this - I had invoked ssh first with the command line option, and it worked. I invoked ssh again with the command line again, but it hung this time. Then I just invoked ssh on its own, and entered the commands one at a time, and it hung again.
Then I ran cygwin directly on the remote server (thinking that it's the VB script causing the problem), so I entered cmd /c update.kcu (without any ssh) and it worked just fine. I checked the CYGWIN setting and it is set to CYGWIN=ntsec tty Christopher Faylor-8 wrote: > > On Thu, May 31, 2007 at 04:27:00PM -0400, Larry Hall (Cygwin) wrote: >>Christopher Faylor wrote: >>> There seems to be some confusion about the CYGWIN tty setting. >>> >>> The only time it should have any effect is when there is a console >>> involved. >>> In that scenario, what effectively happens is that CYGWIN opens up a pty >>> and pretends that the pty is a linux-like tty. >>> >>> Setting CYGWIN=tty for servers should be a no-op. Ditto, having it set >>> while operating under a pty or if there is no console associated with >>> the >>> session. >>> >>> So, if setting CYGWIN=tty actually causes a problem in an ssh session >>> then that is probably a Cygwin bug. Until that problem has become >>> evident >>> lets not assume that there is a problem. >>> >>> I don't mean to be picking on you Larry. You are not the only person >>> I've seen opine about CYGWIN=tty . I remain unconvinced that setting it >>> would present a problem other than the standard problem of running pure >>> Windows programs under a Cygwin pty. >> >>The confusion may come from me. ;-) >> >>So are you saying that all Cygwin services effectively use ptys? >> >>Rereading the original post, I note that KenLee only said 'cmd' was started >>once in the OpenSSH session. I also assumed he invoked 'ssh' from a >>console, which may make a difference if the answer to the above question >>is "no". But that assumption is unsubstantiated by the available >>information. ;-) > > If he ssh'ed to somewhere interactively then there is a pty involved on > the remote end where the program was being run so that's what would have > caused any problem, IMO, regardless of the CYGWIN tty setting on the > local end. In that scenario, since ssh is a cygwin program it shouldn't > care about the CYGWIN=tty setting one way or the other. > > cgf > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > > -- View this message in context: http://www.nabble.com/ssh-session-hangs-while-running-cmd-on-remote-server-tf3848518.html#a10903320 Sent from the Cygwin Users mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
