From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <8ccc8ba40609041325p3a90cfa0nf1184af8bdce0919@mail.gmail.com> Date: Mon, 4 Sep 2006 22:25:05 +0200 From: "Francisco J Ballesteros" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] trying to understand how fork/pipe a filtering program In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200609031909.k83J9UV23187@demeter.cs.utwente.nl> Topicbox-Message-UUID: af18c430-ead1-11e9-9d60-3106f5b1d025 I think there is an example in section 5.4 (or 5.5?) in the draft at http://lsub.org/who/nemo/9.intro.pdf hth On 9/4/06, Skip Tavakkolian <9nut@9netics.com> wrote: just this: in your example, if parent needs to write more than some pipe-buf-limit (i think 32k) to child and/or if child produces output larger than this limit and blocks on the write, it would be a problem. i attached my example of using only one pipe which requires two rendezvous points and customization of the slave proc; this could have a deadlock when a child requires multiple reads to cause a write.