From owner-freebsd-current  Sun Aug  6 05:24:59 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id FAA13531
          for current-outgoing; Sun, 6 Aug 1995 05:24:59 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id FAA13523
          for <current@freefall.cdrom.com>; Sun, 6 Aug 1995 05:24:56 -0700
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id FAA17654; Sun, 6 Aug 1995 05:24:28 -0700
To: Bruce Evans <bde@zeta.org.au>
cc: current@freefall.cdrom.com
Subject: Re: Bug in rlogin? 
In-reply-to: Your message of "Sun, 06 Aug 1995 21:54:11 +1000."
             <199508061154.VAA22351@godzilla.zeta.org.au> 
Date: Sun, 06 Aug 1995 05:24:27 -0700
Message-ID: <17652.807711867@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: current-owner@FreeBSD.org
Precedence: bulk

> >Take one slow net connection, one rlogin session that's got output
> >spewing to it, type ^C.  That rlogin connection is dead, no more,
> >it will never come back.  It is an ex-rlogin session.  OOB data
> >handling a little screwed, perhaps?
> 
> I tried slip at 9600 bps.  It took 8 seconds for output to stop and
> another 8 for control to come back.

And I, of course, am now unable to reproduce it.  Foo! :-)

All I can say is that while I can't reproduce it now, my freefall
windows fall frequent victim to this phenomenon.  So much so, that if
output is spewing out that I know will finish relatively soon, I'll
let it swamp my link for awhile rather than ^C it and destroy the
entire session.

This one must be more subtle than a simple race, that's all I can say!

						Jordan