Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!unido!pcsbst!jkh
From: jkh@pcsbst.UUCP (jkh)
Newsgroups: gnu.bash.bug
Subject: Bad bad bug in Bash 1.01 / SYSV
Message-ID: <928@pcsbst.UUCP>
Date: 19 Jul 89 15:34:53 GMT
Reply-To: jkh@meepmeep.pcs.com ( Jordan K. Hubbard )
Organization: PCS GmbH, Pfaelzer-Wald-Str. 36, 8000 Muenchen; West-Germany
Lines: 25

Running under the dreaded Sys V.2, I get the following behaviour:

bash% sh
$ ^C
bash% $ (shell is still alive, bash is still alive, both want my
         precious input at the same time).

This is really really annoying. Anybody else see this behaviour?

It really screws me up when I'm running something under su and
need to abort it with ^C. Takes me all the way back to my first
bash. Feh. Perhaps some process group problems? Bogus signal handling?
None of the things I've tried so far have worked.

					Jordan

-- 
--------
				Jordan Hubbard
				PCS Computer Systeme GmbH
				West Germany
	UUCP:			{uunet,decwrl}!pyramid!pcsbst!jkh
	ARPA:			jkh@violet.berkeley.edu

Hey! Leave that alone!