Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn )
Newsgroups: net.unix-wizards,net.dcom
Subject: Re: any harm in allowing only ctrl-Q to restart output?
Message-ID: <6934@brl-tgr.ARPA>
Date: Thu, 3-Jan-85 03:30:40 EST
Article-I.D.: brl-tgr.6934
Posted: Thu Jan  3 03:30:40 1985
Date-Received: Sat, 5-Jan-85 02:09:47 EST
References: <247@lsuc.UUCP> <104@redwood.UUCP> <319@rlgvax.UUCP>
Organization: Ballistic Research Lab
Lines: 18
Xref: watmath net.unix-wizards:11344 net.dcom:760

Whether interrupt should unstall output depends on whether one
views DC3/DC1 flow control as user-controlled or as hardware-
controlled.  It is more important to get the hardware working
right, to avoid hung terminals (e.g. VT100 with VT640 graphics,
Teletype 5620).  Most fancy terminals that perform DC3/DC1 flow
control also coordinate this with user scroll control via ^S/^Q
or a scroll/no-scroll key.

There are UNIX terminal drivers that will continue dumping a lot
of characters to a terminal that has tried to stall by sending a
DC3.  The worst offenders are probably those that insist on using
input silo level alarms.  Such terminal drivers are broken and
should be fixed.  (This is possible, since there are also UNIX
terminal drivers that do this right.)

If your users can't be taught that interrupt doesn't automatically
unstall their terminal, then you have other worse problems to
worry about!  Try taping "TYPE CTRL-Q" notes on their terminals.