Error Condition Re: Re: Telnet config at server end

[John Rutherford]

> This is not an answer but a related question. I too played with
> inetd.conf and telnet links to special ports which calls an expect
> script (stolen directly from the expect manual). It works, but
> seems to be very slow, particularly when a search term is entered and
> the return key is pressed. At this stage it takes much longer to
> return results than if I had telnetted directly to the system.
> 
> The script is below:
> 
> #!/usr/local/bin/expect -f
> expect  ;
> spawn telnet system.name
> expect "login:"
> send "username\r"
> interact "\r" {
>         send "\r"
>         expect_user \n {} null
> }
> 
> John Rutherford
> Conn State Univ
> tdowling at ohiolink.ohiolink.edu wrote:
> >
> > Here's a problem my resident Unix wizards can't answer (yet).  I'm
> > trying to set up a series of telnet URLs at different port numbers to
> > connect to different databases (telnet://host:9001 goes to database
> > A, telnet://host:9002 to database B, etc.).  I've learned more about
> > the Unix services and inetd.conf files than I ever wanted, and it
> > actually works...
> >
> > ..except that all the telnet sessions I can create come up in line
> > mode rather than character mode (the Unix telnet client reports that
> > it's in "obsolete linemode"), an annoying detail that completely
> > incapacitates one of our search interfaces.  I've seen this with
> > several browser/telnet combinations, so I'm left assuming that it's
> > controlled at the server end.  Anyone know what I should be doing?
> >
> > Thomas Dowling
> > tdowling at ohiolink.edu