Hung Ultrix LAT sessions?

[Ian! D. Allen [CGL]]

Ever see the situation where you get disconnected from an Ultrix LAT
session, try to resume it without success, say "connect" to start over,
get assigned a different LAT pty and have to log in again, only to
notice your old session still using the other LAT pty, with no way to
get connected to it?  Efforts to echo to (or read from) the other LAT pty
hang?  Then you kill your shell on that LAT pty, and it doesn't die until
you again go back to the DS200 server, connect (and this time you get
your old session LAT pty), and see a flood of waiting output, including
your echo commands, then the shell goes away and the session disconnects?

Obviously the LAT session is disconnected from the DS200, but Ultrix is
trying to flush output through the nonexistent server session and
hanging.  The pty is marked as "in use", so you can't re-connect to
it.  Some kind of killing of the shell (or maybe the TIOCSTI of a break
character I tried) tells Ultrix the pty is free for re-use even though
it still has all that queued up output, so you can now connect to it
and get deluged with queued up output before being disconnected again.

DS200/MC into DS5400, Ultrix 3.1C with mandatory patch tape applied.

The initial fun I had with the flexibility of LAT is rapidly fading
into the depression of realizing the stuff doesn't really work.
-- 
-IAN! (Ian! D. Allen) idallen at watcgl.uwaterloo.ca idallen at watcgl.waterloo.edu
 [129.97.128.64]  Computer Graphics Lab/University of Waterloo/Ontario/Canada