Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ceres.physics.uiowa.edu!news.iastate.edu!IASTATE.EDU!dengholm
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Scripted Telnet's?
Message-ID: <1991May6.092341@IASTATE.EDU>
From: dengholm@IASTATE.EDU (Engholm Daniel M)
Date: Mon, 6 May 1991 14:23:41 GMT
Reply-To: dengholm@IASTATE.EDU (Engholm Daniel M)
Sender: news@news.iastate.edu (USENET News System)
References: <11040@hub.ucsb.edu>
Organization: Iowa State University
Lines: 28

In article <11040@hub.ucsb.edu>, em@topgun.ucsb.edu writes:
> What's your favorite way to automate a segment of a telnet session?
> That is, say you have a tedious, repetitive, and error-prone procedure
> (aren't they all? :->) that you have to go through each time you want
> to log in to a remote host?  What have you done to automate this?
> 
> [stuff deleted]

Along the same lines, I want to connect to a certain Telnet "port" every
time (as opposed to the standard 23).  If I type:

% telnet 129.186.99.23 1001  (to connect to port 1001)

I get connected alright, but the session is in line mode.  I tried to
automate
the process of setting the mode to "character" with little luck.  I
haven't found
a way to specify mode from the command line either.

Any ideas for this one?
--
From my Unix (tm) work-   | Stuck out here in the middle of Iowa with
the
station to yours.         | 'buttaters.  ..or is this Idaho? Ohio????
__________________________|_____________________________________________
________
Don't take life too seriously or you'll never get out of it alive.
--Bugs Bunny