From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
From: Eric Van Hensbergen <ericvh@gmail.com>
In-Reply-To: <z2tfe41879c1004260033q204491f4zfc717d6cf80ffdd1@mail.gmail.com>
Date: Mon, 26 Apr 2010 09:55:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <23E784B6-F189-4DFC-AA82-21CA950DD77D@gmail.com>
References: <k2hfe41879c1004251656id6976800scb02b96f89f5cb40@mail.gmail.com>
	<fba0cac2c9a2d1add33cd834fb31253d@quintile.net>
	<w2lfe41879c1004251750y1cb77ea9ob221543f0506ccb7@mail.gmail.com>
	<A49BBF89-41D7-4AFE-BDCF-D0BF246879CB@gmail.com>
	<z2tfe41879c1004260033q204491f4zfc717d6cf80ffdd1@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Distributed Pipelines
Topicbox-Message-UUID: 0e404b00-ead6-11e9-9d60-3106f5b1d025

The version there is Plan9ports and should work under Plan 9 as well -- =
if it doesn't, beat on Noah :)

     -eric

On Apr 26, 2010, at 9:33 AM, Akshat Kumar wrote:

> Hi Eric,
>=20
> The only reference to PUSH I see is
> at http://code.google.com/p/push
> where the site reads,
>=20
> "This is the new unix port of push."
>=20
> Where might I find the native Plan 9
> version?
>=20
>=20
> Best,
> ak
>=20
>=20
> On 4/25/10, Eric Van Hensbergen <ericvh@gmail.com> wrote:
>> Take a look at Noah's PUSH shell.  It's not there yet, but maybe =
later
>> today.
>>=20
>> Sent from my iPhone
>>=20
>> On Apr 26, 2010, at 2:50 AM, Akshat Kumar
>> <akumar@mail.nanosouffle.net> wrote:
>>=20
>>> Thanks Steve,
>>>=20
>>> rx $cpu 'procdata' | process
>>>=20
>>> works well for one way.
>>> However,
>>>=20
>>> procdata | rx $cpu 'process'
>>>=20
>>> is in the same way as with cpu(1).
>>> Any suggestions for piping in that
>>> direction?
>>>=20
>>>=20
>>> Best,
>>> ak
>>>=20
>>> On Sun, Apr 25, 2010 at 5:40 PM, Steve Simon <steve@quintile.net>
>>> wrote:
>>>>> cpu -c 'procdata' | process
>>>>> ...
>>>>> Perhaps I'm overlooking some simple solutions here.
>>>>> Any suggestions?
>>>>=20
>>>> cpu(1) works by starting exportfs on the remote machine and serving
>>>> the local machines filespace. The remote shell is started with its
>>>> stdin/out/err attached to /mnt/term/dev/cons, thus the command you
>>>> tried will not work (by design).
>>>>=20
>>>> what you want is rx(1) which does exactly what you want, somthing
>>>> like rsh(1) from the Unix world, except it uses plan9' secure
>>>> authentication; e.g.:
>>>>=20
>>>>       rx $cpu | process
>>>>=20
>>>> -Steve
>>>>=20
>>>>=20
>>>=20
>>=20
>>=20
>=20