Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!rochester!ken
From: ken@cs.rochester.edu (Ken Yap)
Newsgroups: comp.windows.x
Subject: Re: signals being ignored by xterm
Message-ID: <1895@sol.ARPA>
Date: Sat, 5-Sep-87 06:31:07 EDT
Article-I.D.: sol.1895
Posted: Sat Sep  5 06:31:07 1987
Date-Received: Sun, 6-Sep-87 03:38:05 EDT
References: <1256@mucs.UX.CS.MAN.AC.UK> <1894@sol.ARPA>
Reply-To: ken@cs.rochester.edu (Ken Yap)
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 23

In article <1894@sol.ARPA> I wrote:
|I saw this before with a user here. What are you starting up the xterm
|with? If it is a sh script with &, then remember sh disables interrupt
|and quit for backgrounded processes. This ignore gets inherited by the
|children. Apparently csh resets before spawning so csh scripts are ok.

Ken, you twit, you shouldn't post articles before breakfast. Ignore
previous distortion of truth.

The user in question was starting up xterm with a backgrounded sh
script.  He was also the rare "/bin/sh login shell" user in our
department.  Since the backgrounded sh script had SIGINT and SIGQUIT
turned off, his xterm sh was ignoring these. Csh, on the other hand,
turns on SIGINT and SIGQUIT catching when it starts up as an interative
shell.  So the other (csh) users never encountered any problem. Xtools
users also had no problems with either login shell.

So, do you have this combination: xterm started from a sh script with &
and a login shell of /bin/sh?

Think I got it right now. Feel better with 3 fresh bagels in my tummy.

	Ken