Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!jade!opal.berkeley.edu!edmoy
From: edmoy@opal.berkeley.edu.UUCP
Newsgroups: comp.windows.x
Subject: Re: Interrupts in xterm windows
Message-ID: <2584@jade.BERKELEY.EDU>
Date: Sat, 21-Feb-87 17:01:17 EST
Article-I.D.: jade.2584
Posted: Sat Feb 21 17:01:17 1987
Date-Received: Sun, 22-Feb-87 15:52:19 EST
References: <10978@lll-crg.ARpA>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: edmoy@opal.berkeley.edu ()
Organization: University of California, Berkeley
Lines: 25
Keywords: xterm interrupt

In article <10978@lll-crg.ARpA> brooks@lll-crg.ARpA (Eugene D. Brooks III) writes:
>We are having a bit of flakyness with ^C in an xterm window.
>Sometimes the running process, like tail for instance, is
>crumped properly and sometimes not.  Has anyone run into this
>problem, and if so how did you solve it.

The only one I know about is if you have a uwm process in background and
open a xterm window from the uwm menu.  Also, the shell that is started
doesn't automatically reset interrupts and quit signals (/bin/sh doesn't
while /bin/csh does).  This is because the standard uwm process has those
signals ignore (because it is backgrounded) and uses a system() call to
evec processes, so the ignore signals get passed on.  Xterm only resets
the hangup signal, so if your shell doesn't fix the interrupt and quit
signals, the ignoring gets passed to all spawned processes.

I've fixed that in my version of uwm, and I could post it if there is
enough interest.

Edward Moy
Academic Computing Services
University of California
Berkeley, CA  94720

edmoy@opal.Berkeley.EDU
ucbvax!opal!edmoy