Xref: utzoo comp.unix.microport:2957 comp.unix.questions:12133 unix-pc.general:2421
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!andante!ulysses!nsscb!rhc
From: rhc@nsscb.UUCP (Rick Calder)
Newsgroups: comp.unix.microport,comp.unix.questions,unix-pc.general
Subject: Re: ct on SysV386 3.0Ue
Message-ID: <696@nsscb.UUCP>
Date: 9 Mar 89 19:07:24 GMT
References: <584@pgthor.UUCP> <7475@killer.DALLAS.TX.US>
Reply-To: rhc@nsscb.UUCP (Rick Calder)
Organization: AT&T NSSC  S. Plainfield, NJ
Lines: 14


	The culprit is uugetty(1M).  See the manpage, it is documented as
a bug that uugetty breaks ct.  If the modem port is idle, ie no uugetty or
getty on it, then ct will work as advertised.  The idea is that there are
2 modem pools, one for incomming, with getty, and one for outgoing, that
are idle.  This is how life was prior to intelligent modems, and ct worked.

		Rick Calder, AT&T National Systems Support Center
				[att!]rick!rick
				attmail!rcalder