Article View: comp.mail.mush
Article #648signals
From: Fletcher Mattox
Date: Sat, 15 Dec 1990 01:37
Date: Sat, 15 Dec 1990 01:37
26 lines
1141 bytes
1141 bytes
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. Like this: % mush -f mailbox Mail User's Shell (7.1.2 7/11/90): Type '?' for help. "mailbox": 0 messages, 0 new, 0 unread Msg 0 of 0: stop Stopped % jobs -l [1] + 8896 Stopped mush -f mailbox % kill -HUP 8896 % jobs -l [1] + 8896 Stopped (tty output) mush -f mailbox % At this point, mush will only die upon receipt of SIGKILL. It has become very important to me to get mush to honor a SIGHUP while suspended. I suspect I can force the issue by turning on ECHO_FLAG in stop_start(), but I would be very grateful for a better solution. Thanks.
Technical Details
Message-ID:
<15847@cs.utexas.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!fletcherShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!fletcher From: fletcher@cs.utexas.edu (Fletcher Mattox) Newsgroups: comp.mail.mush Subject: signals Message-ID: <15847@cs.utexas.edu> Date: 15 Dec 90 01:37:59 GMT Organization: UTexas CS Dept, Austin, Texas Lines: 26