urlichs@smurf.UUCP (Matthias Urlichs) (01/18/89)
I am using the "term" sample program. After a few hours of use, and usually when some modem activity occurs, I am unable to get this program to recognize any events. The mouse can still be moved. The problem seems to occur when carrier on the modem changes. It is not reproducible and usually occurs when causing maximum annoyance. :-) Configuration: A/UX(International) 1.0, one Apple and one old Jasmine 80 HD, 5 MB RAM, networking configured out, 2400 baud modem on tty0, that's it. Has anyone seen this problem? The only fix seems to be hitting the Reset key. I could login on the modem and kill "term", and/or reboot cleanly, but don't have a second computer to do it with. NB: I do not know whether this can occur in the standard console window. This is because I only have a German keyboard and use a slight patch in the "term" program to translate characters. -- Matthias Urlichs -- Humboldtstrasse 7 -- 7500 Karlsruhe 1 -- FRG urlichs@smurf.ira.uka.de -- ++49+721-621127@PTT
dale@ora.UUCP (Dale Dougherty) (02/06/89)
I encountered the problem you describe the other day when I was setting up a UUCP link and testing it. I wasn't quite sure what happened, and I had just recently begun using the TERM program. At any rate, the system hung and I had to reboot to restore it. Wouldn't it be nice if there were some key combination that could kill the login shell and any processes running on the line? It would be the same as typing "kill -9 PID" as superuser from another terminal, and would prevent having to use the reset button to exit abruptly. h ale Dougherty (617) 527-4210 O'Reilly & Associates, Inc., Publishers of Nutshell Handbooks 981 Chestnut Street, Newton, MA 02164 UUCP: uunet!ora!dale ARPA: dale@ora.uu.net
lemke@cherry.ucsb.edu (Steve C. Lemke) (02/07/89)
In article <1446@ora.UUCP> dale@ora.UUCP (Dale Dougherty) writes: }Wouldn't it be nice if there were some key combination that could kill }the login shell and any processes running on the line? It would be }the same as typing "kill -9 PID" as superuser from another terminal, and }would prevent having to use the reset button to exit abruptly. Yes, something written into the kernel of A/UX to watch the keyboard for something unusual, like shift-control-command-power (the little triangle key), which would kill term and whatever else was running. Hmmm... Is anyone on the A/UX development team listening??? I, too, have had the machine lock up on me (outside of term) once when I ran one of the games that came with A/UX!!!