Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!haven!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!pdn!boake2!sherpa!rac
From: rac@sherpa.UUCP (Roger A. Cornelius)
Newsgroups: comp.unix.xenix
Subject: Re: HDB UUCP Problem
Message-ID: <7@sherpa.UUCP>
Date: 8 Feb 89 22:18:40 GMT
References: <5609@turnkey.TCC.COM>
Organization: Personal System Computing, St. Petersburg, FL
Lines: 30

From article <5609@turnkey.TCC.COM>, by sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz):
> I have run across another problem using flow control with Telebit-Plus
> modem! This one seems to be in uucico. If I have a user log into the system,
> using a standard shell, and I do a "stty" on the port, ctsflow is enabled
> < I call it out in my gettydefs file >. HOWEVER, when I do a "stty" command
> while a uucp transfer is in progress at 19.2K baud, I get returned
> a -ctsflow !!!!!!  It seems that SCO must be doing an ioctl call in uucico
> which removes the preset terminal parameters. Actually, they should since
> uucp should be running at 8N1. But CTSFLOW SHOULD NOT BE REMOVED if enabled!

I've got the same problem on the 286 version (2.2.3).  If I dial out on
the line (using cu or uucp with SCO's dialTBIT), and then do a
stty -a <tty?? it shows both -ctsflow and -rtsflow.

Dial-ins do show ctsflow enabled when I have only CTSFLOW enabled in
gettydefs.  But if I put both CTSFLOW and RTSFLOW in gettydefs and then
dial in on the line, the port locks up as soon as I enter the password,
and I can't get past that point.  It appears that RTSFLOW is not
supported.

> I have sent two requests already to SCO for their CTS/RST Flow control
> patches; however, I have not heard a single word from them. I am wondering
> if one of the patches is to uucico to allow the preset getty/gettydef
> parameters to be used without changes in uucico.

I spoke with tech support Monday (02/06) and they put me on the list to
receive the fix when engineering finishes with it.

Roger        rac@sherpa
			 uunet!sherpa!rac