>{ }

>{ }

[Paul D. Swasey]

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