From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
Date: Sun, 25 Apr 2010 16:56:47 -0700
Message-ID: <k2hfe41879c1004251656id6976800scb02b96f89f5cb40@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
Subject: [9fans] Distributed Pipelines
Topicbox-Message-UUID: 0ddb70f4-ead6-11e9-9d60-3106f5b1d025

In running some computationally intensive processes
between my terminal(s) and cpu server(s), I noticed
a problem in trying to join data together by a pipeline:

procdata | cpu -c 'process'

doesn't really send the output of `procdata' to `process',
as the latter is being run on a CPU server. Since there
are some use cases where `procdata' might take a long
time to get to EOF (or possibly may never reach it), it
isn't in my interest to first send the output of `procdata'
to a file and then run `process' on the CPU after it's
finished.
Likewise, there is the inverse problem:

cpu -c 'procdata' | process

outputs to rio terminal instead of sending output to `process'.
It seems to me that the two problems would have similar
solutions.

Perhaps I'm overlooking some simple solutions here.
Any suggestions?


Best,
ak