dave@andromeda.rutgers.edu (Dave Bloom) (01/17/89)
I've just brought up OSx4.4 with the att init-getty-login package, and a funny thing happens: when you log in on a regular terminal or pty with a default sh or ksh, ^C processing is screwy. A ^C DOESN'T interrupt the current process. (Though the stty command shows the settings are as they should be.) Starting up a csh makes interrupt processing work fine, but exit out of that csh to the top shell and it restores the terminal to the screwy state. My guess is that there's something wrong with the 4.4 att getty, leaving the terminal in a half baked mode. Since Pyramid ONCE AGAIN is taking their sweet time sending us our source, I'm wondering if anyone else out there has seen this problem. Thanx. _______________________________________________________________________________ rutgers\ | Dave Bloom galaxy >!andromeda!dave -or- dave@andromeda.rutgers.edu | Work: (201)648-5085 pyramid/ |
csg@pyramid.pyramid.com (Carl S. Gutekunst) (01/19/89)
In article <1602@galaxy> dave@andromeda (Dave Bloom) writes: >I've just brought up OSx4.4 with the att init-getty-login package, >and a funny thing happens: when you log in on a regular terminal >or pty with a default sh or ksh, ^C processing is screwy. A ^C >DOESN'T interrupt the current process. Sounds like someone broke /etc/profile, and forgot to turn the traps off. There should be a line like: trap 1 2 3 at the end of the file. If this is missing (or /etc/profile is exiting early), ^C will cause a little lost output, but the program will continue to run. Csh sets its own signal traps, so when you invoke it ^C works again. <csg>
msh@otc.otca.oz (Michael Homsey) (01/24/89)
check that the /etc/profile file has trap commands set properly. msh