From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26360 invoked from network); 9 Jun 2006 09:52:10 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.3 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 9 Jun 2006 09:52:10 -0000 Received: (qmail 80179 invoked from network); 9 Jun 2006 09:52:02 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 9 Jun 2006 09:52:02 -0000 Received: (qmail 12389 invoked by alias); 9 Jun 2006 09:51:52 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10366 Received: (qmail 12373 invoked from network); 9 Jun 2006 09:51:51 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 9 Jun 2006 09:51:51 -0000 Received: (qmail 79038 invoked from network); 9 Jun 2006 09:51:51 -0000 Received: from vms048pub.verizon.net (206.46.252.48) by a.mx.sunsite.dk with SMTP; 9 Jun 2006 09:51:47 -0000 Received: from torch.brasslantern.com ([71.116.105.50]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0J0L00MFX7E8OMK1@vms048.mailsrvcs.net> for zsh-users@sunsite.dk; Fri, 09 Jun 2006 04:51:45 -0500 (CDT) Received: from torch.brasslantern.com (localhost.localdomain [127.0.0.1]) by torch.brasslantern.com (8.13.1/8.13.1) with ESMTP id k599pipA004856 for ; Fri, 09 Jun 2006 02:51:44 -0700 Received: (from schaefer@localhost) by torch.brasslantern.com (8.13.1/8.13.1/Submit) id k599phGp004855 for zsh-users@sunsite.dk; Fri, 09 Jun 2006 02:51:43 -0700 Date: Fri, 09 Jun 2006 02:51:43 -0700 From: Bart Schaefer Subject: Re: Bi-directional pipe In-reply-to: <44893A14.9040906@yahoo.fr> To: zsh-users@sunsite.dk Message-id: <060609025143.ZM4854@torch.brasslantern.com> MIME-version: 1.0 X-Mailer: OpenZMail Classic (0.9.2 24April2005) Content-type: text/plain; charset=us-ascii References: <4486CBA2.9030501@yahoo.fr> <060608202844.ZM10410@torch.brasslantern.com> <44893A14.9040906@yahoo.fr> Comments: In reply to Guillaume Chazarain "Re: Bi-directional pipe" (Jun 9, 11:06am) On Jun 9, 11:06am, Guillaume Chazarain wrote: } } My solution is to do something like this: } echo "$LARGE_REQUEST" >&p & } read REPLY <&p In that case you don't have only two processes. If one process "knows" to fork for large writes, that process is prepared for the situation. Most read-stdin/write-stdout unix commands that one might execute are not so prepared, is my point.