^C in rlogin hangs systems

[raj at UCI-750A.ARPA]

From:  Richard Johnson <raj at UCI-750A.ARPA>

We have 3 Vax 750s running 4.2BSD connected together via ethernet using
3-COM boards.  About once or twice a month someone will be logged in
from system "A" across the network to system "B", will type ^C twice
(or more), and will hang both systems "A" and "B".  Every core dump we
look at shows that the system seems to still be running normally.  It
appears that it's caught at a high priority level.  Typing on user
terminals doesn't even echo.  Input from the console *is* echoed but
that's all.  We have found that rebooting one of the two systems results
in the other one being freed.

We believe this always happens after the person types ^S followed by
the above mentioned ^C's.  Some of us have a theory that the hanging
has something to do with the output queues from system "B" getting full
since the ^S is done locally on system "A".

Has anyone else observed this problem?  Was a fix for this posted which we
missed?  Any help would be greatly appreciated.

------------------------------------------------------------------------
Richard Johnson                             raj at uci               (ARPA)
UCI ICS Systems Manager                     ucbvax!ucivax!raj     (UUCP)