From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0fdf1724083db9d68cc2e1d3c5a0bc7e@vrtra.net>
To: 9fans@9fans.net
Date: Wed, 16 May 2012 00:35:09 -0700
From: 9@vrtra.net
In-Reply-To: <041beafe28d237c7ab5edbd2ad94bace@sp.inri.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] rc behavior with rfork
Topicbox-Message-UUID: 8e114202-ead7-11e9-9d60-3106f5b1d025

Hi,
  Here is some thing that tripped me up.
First from a shell script, execute an echo and direct it to a file in
/env (essentially setting that variable).  However the command does
not seem to have any effect

cpu% @{rfork e; echo hi} > /env/hi cpu% cat /env/hi

And it is specific to the filesystem interface of env

cpu% @{rfork e; echo hi} > /tmp/hi cpu% cat /tmp/hi hi

And this is somehow connected to rfork

cpu% {echo hi} > /env/hi cpu% cat /env/hi hi

On the otherhand, putting any command in the chain makes the behavior
disappear.

cpu% @{rfork e; echo hi} |cat > /env/hi cpu% cat /env/hi hi

My question is, is this intensional?  It feels as if there is a
leakage here of the rfork when its effect is felt beyond the braces,
and it feels odd for the two fs interfaces to behave differently (even
though one of them is special)

vrtra