From: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
To: rc@archone.tamu.edu
Subject: Re: signals and suchlike
Date: Fri, 14 Feb 1992 23:00:57 -0600 [thread overview]
Message-ID: <92Feb15.000103est.2743@hawkwind.utcs.toronto.edu> (raw)
A bug in signal handling: rc unconditionally ignores a SIG_IGN'd
SIGINT, even if it's running a shell. It should not; if SIGINT is
ignored on entry to a shell script, rc should not change this. Only
when it's interactive is it entitled to play around with signals in
that way.
- cks
next reply other threads:[~1992-02-15 5:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-02-15 5:00 Chris Siebenmann [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-02-16 1:50 Tom Culliton x2278
1992-02-15 4:08 schwartz
1992-02-15 4:39 ` Chris Siebenmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92Feb15.000103est.2743@hawkwind.utcs.toronto.edu \
--to=cks@hawkwind.utcs.toronto.edu \
--cc=rc@archone.tamu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).