Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.bugs.4bsd
Subject: Re: rlogin drops output when stop/start characters change
Message-ID: <1452@umcp-cs.UUCP>
Date: Fri, 30-Aug-85 22:45:16 EDT
Article-I.D.: umcp-cs.1452
Posted: Fri Aug 30 22:45:16 1985
Date-Received: Sun, 1-Sep-85 05:49:53 EDT
References: <3216@mordor.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 20

(Oops, one more.  I do not wish to seem wroth with your fix: rlogin's
handling of out of band data has long been a sore point with me,
and you have finally prodded me enough that I am investigating it.)

> "rlogind" also sends an out-of-band message if it receives a
> TIOCPKT_FLUSHWRITE packet from the master side of the pty.  (I
> haven't look at the code myself, but I'm told that the kernel never
> produces this packet type.)

Ah, but it does!  Look at the code for ptsstop and note the comment;
and compare the values of TIOCPKT_FLUSHREAD and FREAD, and those of
TIOCPKT_FLUSHWRITE and FWRITE.  Recall that a TTY stop routine is
called both for flow control (^S/^Q) and for I/O flushes (TIOCFLUSH
and signals).

The new code is certainly correct; I hope the kernel is as well.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland