Very Computer

When running shl on the console, if a console message appears, like
"Uugetty respawning too rapidly", it puts the terminal in a state where
whatever I type is echoed, but nothing is recognized, and ^Z does not do
anything.  I have to go to another terminal and kill the shl process.

Does anyone know why this happens?  It is probably one of those internal
things that can't be corrected.

I am writing a shl clone that exhibits the same behavior.

--
Bruce Momjian           | 830 Blythe Avenue               | home: (215)853-3000

ADDITIONAL INFORMATION:

I have found that typing:

        echo hello >/dev/console

returns immediately and sends nothing to the console screen during
normal shl operation.  After a console warning message appears, an echo
to the console from another tty does appear on the screen.  It is as
though the console device is hybernating during shl operation, but takes
control during console messages and doesn't give control back.

I hope this might help someone figure out how I might avoid this in my
shl clone.
--
Bruce Momjian           | 830 Blythe Avenue               | home: (215)853-3000