From: iwane@lit.rd.nttdata.jp (Kazumi Iwane)
To: rc@hawkwind.utcs.toronto.edu
Subject: rc-1.5betadev-1 sigexit problem
Date: Tue, 25 Jul 1995 05:08:26 -0400 [thread overview]
Message-ID: <9507250908.AA24499@taxis.lit.rd.nttdata.jp> (raw)
hello rc fans,
i found a peculiar sigexit behavior of rc 1.5betadev-1
(no readline). the following script ("test") illustrates
it:
--------------------------------------------------------
; cat test
fn sigexit { echo sigexit $status }
{ echo hi | cat } > test.out
; /usr/local/bin/rc.1.5 test
sigexit 0
; cat test.out
hi
sigexit 0 0
;
--------------------------------------------------------
it seems that an extra sigexit is called when:
command grouping is used,
the last command of the group is a pair of
piped processes,
and the grouped commands output is redirected.
this behavior is seen both on sun ss10 (sunos 4.1.3) and
hp 9000/715 (hp-ux 9.05). rc-1.4 behaves as one would expect
(only one sigexit at the end of the script). i fiddled with
the code a little but could not come up with cure.
can someone help?
--
iwane@lit.rd.nttdata.jp
"This is where the future lies beneath the burning sulphur skies."
-- C.Hynde, 'Downtown (Akron)'
reply other threads:[~1995-07-25 9:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9507250908.AA24499@taxis.lit.rd.nttdata.jp \
--to=iwane@lit.rd.nttdata.jp \
--cc=rc@hawkwind.utcs.toronto.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).