rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: schwartz@groucho.cs.psu.edu
To: rc@archone.tamu.edu
Subject: signals and suchlike
Date: Fri, 14 Feb 1992 22:08:13 -0600	[thread overview]
Message-ID: <92Feb14.230816est.2538@groucho.cs.psu.edu> (raw)


Using rc-1.3b, some questions about signals...

; whatis sigint		# implicitly ignored, right?
sigint not found	# so why not say so?
; fn sigint {}		# set to ignored
; whatis sigint		# not the same?
fn sigint {}		# hmm

The man page says that signals are reset to their default
values in subshells.  CHANGES says that ignored signals
stay ignored.   It seems like the man page is correct, though:

; cat x
#!/bin/rc
whatis sigint
sleep 100000

; hup x		# hup runs x in the process group of the tty, so it
		# receives signals, but also sets sigint to sig_ign.
sigint not found
; ^C		# this kills x.

An analogous /bin/sh script behaves as expected.



             reply	other threads:[~1992-02-15  4:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-02-15  4:08 schwartz [this message]
1992-02-15  4:39 ` Chris Siebenmann
1992-02-15  5:00 Chris Siebenmann
1992-02-16  1:50 Tom Culliton x2278

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=92Feb14.230816est.2538@groucho.cs.psu.edu \
    --to=schwartz@groucho.cs.psu.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).