From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <7763d735e69d8028c5acb643c6b90b13@coraid.com> References: <23E784B6-F189-4DFC-AA82-21CA950DD77D@gmail.com> <7763d735e69d8028c5acb643c6b90b13@coraid.com> Date: Mon, 26 Apr 2010 14:57:42 -0700 Message-ID: From: Akshat Kumar To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Distributed Pipelines Topicbox-Message-UUID: 0ea707d2-ead6-11e9-9d60-3106f5b1d025 Hi Erik, Thanks for figuring that bit out! Indeed, it seems TCP is the problem, and IL seems to work fine for me for the moment: echo '1 2 3' | rx il!$cpu!17009 awk -f $home/comp.awk | gview works perfectly! I'll try to dig deeper into the TCP case. Best, ak On 4/26/10, erik quanstrom wrote: >> >> "... >> eqn paper | rx kremvax troff -ms | rx deepthought lp >> Parallel processing: do each stage of a pipeline on a >> different machine. >> " >> >> however, it seems not to work this way. >> My basic test has been something like: >> >> echo '1 2 3' | rx $cpu awk -f $home/comp.awk | gview > > cool that you tracked this down. > > this just doesn't work. the problem seems to be that tcp > is eating the eof. awk doesn't know to exit. > > if you are using il, this does work. > > ; echo 1 2 3| 8.rx bureau sed s/1/x/ | sed s/2/y/ > x y 3 > > but if you are using tcp, it hangs. sed never sees the > eof and doesn't generate output (because it's buffered). > > the answer isn't obvious to me with tcp as i don't > know of a way to half-close a tcp connection =97 > from userspace anyway. > > - erik > >