From:	joz AT mentor-systems DOT com (Jonathan Storey)
Subject:	remote.tar.gz remote utilites - problems 'inetd?'
18 Jun 1998 11:32:32 -0700 :
Message-ID:	<000b01bd9aa4$e524a520$050120c0.cygnus.gnu-win32@menpc5>
Mime-Version:	1.0
To:	<gnu-win32 AT cygnus DOT com>

 NT-WKS4-SP3

 /bin/sh.exe -> /bin/sh.exe.old
 /bin/sh.exe is a copy of /bin/bash.exe

My inetd runs as an NT service successfully (according to NT)
but attempting to telnet etc. to my NT box, fails as though inetd
were not running. As a temporary soloution I got around this by
just executing 'inetd -d' from the command line and leaving it
running in a minimised window.

When I telnet to my NT box the shell is 'there' but stdin/stdout are
mixed up:

   echo TEST >/dev/tty  - outputs 'TEST' in the window running inetd.
   echo TEST >&2 - outputs 'TEST' in the output window of my session

commands typed are not echo'd, but the output of 'ls' for example is OK.

I have tried other shells, including pd-ksh, and although these have other
problems the stdin/out probs don't exist, I can see my prompt etc.

Anyone any ideas what I might be doing wrong, or how to get 'bash' to
operate
correctly when I telnet ? - anyone getting similar problems ?.....

I know there are some strange and hidden behaviours of connecting
stdin/stdout
with regards to sockets under Windows etc., but I presume other people are
already successfully using this software in it's present form.

Answers/Suggestions/... greatly appreciated

Regards,
		JOZ.

Systems Analyst/Programmer
Tech. Research + Development
Mentor Systems plc

(joz AT thinktank DOT demon DOT co DOT uk)
(joz AT mentor-systems DOT com)


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -