From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 26 Apr 2010 00:33:04 -0700 Message-ID: From: Akshat Kumar To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [9fans] Distributed Pipelines Topicbox-Message-UUID: 0e331cb4-ead6-11e9-9d60-3106f5b1d025 Hi Eric, The only reference to PUSH I see is at http://code.google.com/p/push where the site reads, "This is the new unix port of push." Where might I find the native Plan 9 version? Best, ak On 4/25/10, Eric Van Hensbergen wrote: > Take a look at Noah's PUSH shell. It's not there yet, but maybe later > today. > > Sent from my iPhone > > On Apr 26, 2010, at 2:50 AM, Akshat Kumar > wrote: > >> 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 >> 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.: >>> >>> rx $cpu | process >>> >>> -Steve >>> >>> >> > >