From owner-freebsd-hackers  Wed Nov 15 21:27:29 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA21145
          for hackers-outgoing; Wed, 15 Nov 1995 21:27:29 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA21128
          for <hackers@FreeBSD.org>; Wed, 15 Nov 1995 21:27:23 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA03381; Thu, 16 Nov 1995 16:18:21 +1100
Date: Thu, 16 Nov 1995 16:18:21 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199511160518.QAA03381@godzilla.zeta.org.au>
To: ache@astral.msk.su, bde@zeta.org.au, stesin@elvisti.kiev.ua,
        tateoka@pdcd.ilab.toshiba.co.jp
Subject: Re: Is TTYHOG too small? (Re: STARTECH ...550CP chips are Ok for me. )
Cc: hackers@FreeBSD.org
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

>>Are you using hardware flow control in both directions?  I think uucp's
>>`hardflow' option only applies to outgoing connections.  To initialize
>>crtscts flow control for uucp logins (and all other logins), use
>>`stty crtscts' on the initial state ports and perhaps on the lock state
>>ports for each dialin port.  See /etc/rc.serial.

>No, uucp set _both_ iflow & oflow.

Of course CRTSCTS sets flow control in both directions.  uucp doesn't
even know about FreeBSD's CRTS_IFLOW and CCCTS_OFLOW which can be used
in both directions.

I mean that `hardflow y' in the /etc/uucp/port has no effect of uucp logins.

Bruce