Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!dali.cs.montana.edu!ogicse!schaefer
From: schaefer@ogicse.ogi.edu (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: signals
Message-ID: <15187@ogicse.ogi.edu>
Date: 19 Dec 90 08:32:07 GMT
References: <15847@cs.utexas.edu>
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR
Lines: 11

In article <15847@cs.utexas.edu> fletcher@cs.utexas.edu (Fletcher Mattox) writes:
} When mush receives a SIGTSTP followed by any other signal, it
} blocks trying to write something (the prompt?) to the tty.  After
} the second signal is received, it is in a hopelessy confused
} state and seems to ignore all signals.  Especially SIGHUP.

Remove the print() calls in catch() (signals.c) that try to print the
signal name from sys_siglist[].  That should do it.
-- 
Bart Schaefer						schaefer@cse.ogi.edu
ZipCode Software Corporation				schaefer@zipcode.com