From: Alan Watson <alan@oldp.lowell.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: rc handler/exec problem?
Date: Sat, 10 Jun 1995 20:46:13 -0400 [thread overview]
Message-ID: <9506110046.AA16136@oldp.lowell.edu> (raw)
After months (years?) without a problem, I've come across this little
weirdo in rc.
It would seem that rc is having problems generating the argument list
for an exec in the signal handler. I first noticed this problem while
trying to exec /bin/kill -TERM $apids from a sigint handler, as I got
nothing but usage and <junk>: No such file or directory errors. I've
reproduced it with /bin/echo (below).
This happens on Alphas running v2.0 and v3.2 OSF/1.
Someone please tell me I've done something really dumb. Be charitable
and blame it on working too hard.
Alan
; cat sigint.rc
/bin/echo foo
sleep 10 &
fn sigint { /bin/echo foo }
sleep 10
; rc -x sigint.rc # and hit control-c
/bin/echo foo
foo
sleep 10
fn sigint {/bin/echo foo}
sleep 10
/bin/echo foo
`}: No such file or directory
next reply other threads:[~1995-06-11 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-06-11 0:46 Alan Watson [this message]
1995-06-11 1:44 Byron Rakitzis
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=9506110046.AA16136@oldp.lowell.edu \
--to=alan@oldp.lowell.edu \
--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).