From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <607a20438a5616b740652fc1bc04c986@sp.inri.net> References: <0fdf1724083db9d68cc2e1d3c5a0bc7e@vrtra.net> <607a20438a5616b740652fc1bc04c986@sp.inri.net> Date: Wed, 16 May 2012 15:21:10 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0ce03a16ea86a004c02807e6 Subject: Re: [9fans] rc behavior with rfork Topicbox-Message-UUID: 8f290bac-ead7-11e9-9d60-3106f5b1d025 --000e0ce03a16ea86a004c02807e6 Content-Type: text/plain; charset=UTF-8 most /env things haven't got newlines so wc -l /env/* generally gives 0. you also need to watch the binding in things like this: 2012/5/16 > @{rfork e; echo hi} >/env/hi ie, the env file might be created in the parent name space, because the > is done before the @, and in the scope above the rfork e, compared to term% @{rfork e; echo hi >/env/hi} term% ls /env/hi ls: /env/hi: '/env/hi' file does not exist --000e0ce03a16ea86a004c02807e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable most /env things haven't got newlines so wc -l /env/* generally gives 0= .
you also need to watch the binding in things like this:

2012/5/16 <sl@9front.org>
@{rfork e; echo hi} >/env/hi
=

ie, the env file might be created in the parent name s= pace, because the > is done before the @,
and in the scope above the rfork e, compared to

term% @{rfork e; echo hi >/env/hi}
term% ls /env/hi
ls: /env/hi: '/env/hi' file does not exist

--000e0ce03a16ea86a004c02807e6--