From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <fba0cac2c9a2d1add33cd834fb31253d@quintile.net>
References: <k2hfe41879c1004251656id6976800scb02b96f89f5cb40@mail.gmail.com>
	<fba0cac2c9a2d1add33cd834fb31253d@quintile.net>
Date: Sun, 25 Apr 2010 17:50:35 -0700
Message-ID: <w2lfe41879c1004251750y1cb77ea9ob221543f0506ccb7@mail.gmail.com>
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Distributed Pipelines
Topicbox-Message-UUID: 0de37934-ead6-11e9-9d60-3106f5b1d025

Thanks Steve,

rx $cpu 'procdata' | process

works well for one way.
However,

procdata | rx $cpu 'process'

is in the same way as with cpu(1).
Any suggestions for piping in that
direction?


Best,
ak

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?
>
> 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).
>
> 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.:
>
> =A0 =A0 =A0 =A0rx $cpu | process
>
> -Steve
>
>