From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <fba0cac2c9a2d1add33cd834fb31253d@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Mon, 26 Apr 2010 01:40:16 +0100
To: 9fans@9fans.net
In-Reply-To: <k2hfe41879c1004251656id6976800scb02b96f89f5cb40@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Distributed Pipelines
Topicbox-Message-UUID: 0ddf5c3c-ead6-11e9-9d60-3106f5b1d025

> 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.:

	rx $cpu | process

-Steve