From: "Paul D. Swasey" <ps3u+@andrew.cmu.edu>
To: rc@archone.tamu.edu
Subject: >{ }
Date: Wed, 30 Oct 1991 14:44:51 -0600 [thread overview]
Message-ID: <0d3lb3200aw9AlCYED@andrew.cmu.edu> (raw)
First rc prompts are sent to fd 2. This isn't realy related to the
problem but is there some reason for it?
exec >>[2] >[2]{ sed 's/^/ERROR: /' }
Does wierd things (on a system without /dev/fd, at least -- Ultrix
4.2). Why the wait: no children?
---------------- (no hang, use pipe on first command)
; cd
; ls .rcrc .nothere
.nothere: No such file or directory
.rcrc
; exec >>[2] >[2]{ sed 's/^/ERROR: /' }
ls .rcrc .nothere
.rcrc
ERROR: ; .nothere: No such file or directory
ERROR: wait: No children
echo doing things now
doing things now
echo even doing this >[1=2]
ERROR: ; ; even doing this
pwd
/afs/andrew.cmu.edu/usr16/ps3u
^D
Process cmushell finished
---------------- (hang)
; exec >>[2] >[2]{ sed 's/^/ERROR: /' }
echo ignores stderr
ignores stderr
pwd
Process cmushell killed
---------------- (hmm, let's try non-buffering output -- hang)
; exec >>[2] >[2]{ cat -u }
; echo ignoring stderr?
ignoring stderr?
Process cmushell killed
---------------- (line buffering input (i think)? -- nohang)
; echo '#!/bin/sh
while read line; do echo $line; done' > $h/u/sh
; chmod +x $h/u/sh
; exec >>[2] >[2]{ $h/u/sh }
echo no stderr usage
no stderr usage
; wait: No children
wait: No children
wait: No children
wait: No children
pwd
/usr/tmp/ps3u
echo is it working >[1=2]
; ; is it working
^D
Process cmushell finished
----------------
-dave
ps3u+@andrew.cmu.edu
R746PS3U@VB.CC.CMU.EDU
reply other threads:[~1991-10-30 20:46 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=0d3lb3200aw9AlCYED@andrew.cmu.edu \
--to=ps3u+@andrew.cmu.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).