-
Notifications
You must be signed in to change notification settings - Fork 28
Description
I am running:
- procServ build from upstream sources (GitHub) on cygwin64 serving to port 12345
- child: a native Windows64 built 3.15 (bazaar trunk) IOC: just the softIoc exe from Base
When I connect using 'nc -C' on cygwin:
The connection is running in "line mode". (Control chars are sent on hitting Enter.)
Prompt is double: "epics> epics> ".
I see every character as it is typed, plus it is echoed once I hit Return: I get the another echo of the commend and an empty line before the result.
When I connect using 'nc' on cygwin:
The connection is running in "line mode". (Control chars are sent on hitting Enter.)
Prompt is single: "epics> ".
I see every character as it is typed, plus it is echoed once I hit Return: I get the another echo of the commend (no empty line) before the result.
When I connect using PuTTY (telnet mode):
The connection is running in "line mode". (Control chars are sent on hitting Enter.)
Prompt is single: "epics> ".
I do not see characters as they are typed, it is echoed once I hit Return: I get the another echo of the commend (no empty line) before the result.
When I connect using native 'telnet' on Windows:
The connection is running in "char mode". (Control chars are sent immediately.)
Prompt is double: "epics> epics> ".
I see every character as it is typed, once I hit Return I get an empty line before the result.
When I connect using 'telnet' on cygwin:
The connection is running in "char mode". (Control chars are sent immediately.)
Prompt is single: "epics> ".
I see every character as it is typed, no additional echoes, result follows immediately.
This last mode is actually flawless and exactly the wanted behavior.
I would say that the issue is not between procServ and the IOC, but between the client and procServ.