Path: utzoo!mnetor!uunet!husc6!mit-eddie!minya!jc
From: jc@minya.UUCP (John Chambers)
Newsgroups: comp.unix.wizards
Subject: ^C works strangely on this terminal.
Message-ID: <435@minya.UUCP>
Date: 21 Dec 87 03:02:36 GMT
Organization: home
Lines: 28

Hi there.  You might remember a month or so ago I described a bit 
of unusual behavior, in which this terminal somehow ignored ^C, 
although we have the the usual setup where stty says:
	intr = ^c; quit = ^x; erase = ^h; kill = ^z; swtch = ^`; 

Nobody came forth with a useful response to that one.  But I have
some further evidence now.  As part of installing the recent solution
to the question of how you get `pwd` into PS1 in a Bourne shell, I
turned off a line in our /etc/profile that used to say:
	trap "" 1 2 3

This line apparently caused the strange behavior, since it no longer
happens.  What happens instead is even more curious.  Now ^C causes
the running program to die, and also the shell dies, logging me out!

I've seen this behavior before; I have another program which, when 
it exits normally, the shell also exits (though I wouldn't call that
'normally' :-).  Why, I'm not sure.  But I suspect that what is going
on is that a signal is going to both my program and also to the shell.

Does anyone have any explanation?  Is there a reliable way to get a
Sys/V to automagically pass signals to both a process and also to its
parent?  Is there a way to make it stop doing this?  Is this all just
a fignewton of my imagination?  Stay tuned....


-- 
John Chambers <{adelie,ima,maynard,mit-eddie}!minya!{jc,root}> (617/484-6393)