This is the mail archive of the
mailing list for the Cygwin project.
Executable hang when using a cygwin telnet session
- From: "Chris Lidgate" <lidgaca at lycos dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 10 Jun 2003 08:18:36 -0700
- Subject: Executable hang when using a cygwin telnet session
- Organization: Lycos Mail (http://www.mail.lycos.com:80)
- Reply-to: lidgaca at lycos dot com
I have just seen something that seemed very odd, and I can't find any information about it that seems relevant in any of the usual places.
A colleague is developing a win32 console cli program that does some useful stuff ... We've been testing it physically on our win2000 box under a normal dos prompt - and it works fine. We can also run the program from a BASH shell if I physically open the cygwin shell on the win2000 console. Again the new program does all of the stuff I would expect.
Then I had a great idea, if we could telnet into our win2000 box we could put several people onto the testing of the new program. If I telnet into the box under the normal cygwin telnetd service, the program hangs (in the program loader ?) without producing any output at all (normally the first thing it does is printf a version / wellcome header). CRTL C will bring back the bash session, but the cli program refuses to run.
HOWEVER, all of the normal win32 console apps (tracert, ipconfig, yadda yadda yadda) run perfectly well from the telnet session. I'm sure there is nothing wrong with inetd or telnetd as we use it quite a lot, but it's as if I'm missing something fundemental.
Does anyone know why this program would behave like this and know if there are any workarounds ??
Chris Lidgates private email |
This email address is |
lidgaca AT lycos DOT com |
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html