Simon Casady <email@example.com> wrote:
On 12 Mar 2004 23:57:33 GMT, Robert Krten <> firstname.lastname@example.org> > wrote:
Is there a pseudo-tty wrapper that I can jam into inetd.conf that
will do the “magic” of binding a master/slave side of a pty on
a spawned process? I want to be able to start an arbitrary “regular”
TCP/IP-unaware program when someone telnets to a particular port.
Currently, the TCP/IP-unaware program needs to have the following
parameters set on the telnet session:
as well as some judicious use of “fflush” on stdout… A pain.
I am not sure I understand. Inetd is designed to start tcp/ip unaware
programs. Do you want to automatically login a telnet session and
start a program ? Then perhaps you want rlogind.
I’m probably the one who doesn’t understand
I wrote a chess program that uses “fgets” to get data from stdin.
I’m expecting the user to simply “telnet” to a given port on my
When I put the chess program in inetd, the user has to hit ^J
to cause a newline to be entered, rather than just hitting return.
Also, characters from the user aren’t echoed.
So, in short, the way that inetd starts the program, and the
way that the telnet client program accesses said programs is
different (in an annoying way) than what a user gets when they
login to a pty-controlled session and run a program…
I (naively) thought that if I could put a pty between the inetd
end of things and the “regular, TCP/IP unaware program” end of
things, that these problems would go away…
Am I confused?
Using M2, Opera’s revolutionary e-mail client: > http://www.opera.com/m2/
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/