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. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/
