Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ncar!boulder!daemon
From: BILLW@mathom.cisco.com (WilliamChops Westfield)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: ASM Terminal Server and uucp
Message-ID: <27802@boulder.Colorado.EDU>
Date: 9 Oct 90 20:42:03 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 28

Sigh.  Usually, I try to put more useful information in the messages
I send out.  I guess I'll have to try again...

    Is anybody successfully using a cisco terminal server with uucp?  If so,
    I'd be very interested in hearing what you had to do to get it working.

    I have turned off all flowcontrol and set databits to 8 and set no escape
    character.  Maybe I have left something out of the line configuration?

You might want "telnet transparent" also.  Note that the "terminal download"
exec command changes all of these parameters with one command.  "autohangup"
will cause the terminal server to hang up when the last connection has been
closed, which is useful since uucp apparently doesn't know how to do any
"post logout" commands...

In general, both the terminal server and the host will be happier if
you establish a stream connection directly to the uucp-over-tcp port
on the unix system (this way you avoid a pty on the unix host!).  In
this case, the commands on the terminal server would look something like:

	TS>terminal download
	TS>terminal autohangup
	TS>telnet unixsystem uucp /stream


Bill Westfield
cisco Systems.
-------