KenLee wrote: > 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 >
As Chris mentioned, the 'tty' setting would only have an effect when you went to the remote server and ran the command there. Since you saw no problem doing that, that indicates ptys aren't an issue here. Is the Windows 'rsh' command available on the server? If so, you could use it to determine if the VB script does something that just isn't reliable remotely. -- 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/
