From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8177 invoked by alias); 27 Jul 2015 09:34:48 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35927 Received: (qmail 25140 invoked from network); 27 Jul 2015 09:34:48 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=secretsauce.net; h=content-type:date:from:message-id:mime-version:subject:to :x-sasl-enc:x-sasl-enc; s=mesmtp; bh=qrtiyWVfgB6BTN7hpiwGYTZn8qc =; b=HJOHbCMIVxXY4Hc1tFU1Rm3pQbJdczs9kTDnWe0pZTpwuLzjh274DRCjlav xXOczZsS/sTSMd3Csb4RhU8giWO0DQOpZOdF3UBuivB5YMA5oUNFwmKjaN7Q1UZn W/68byuIjpIzJi89JkIWS/ZlCR72krX6emd5h/Zn901CcWFg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=qr tiyWVfgB6BTN7hpiwGYTZn8qc=; b=pz5+MEPMkEFRAgr9ylJMXH/89q06tp+I7v B4+y5S1n0BR6+B6lwxxVTpHHbCea4hhi+BeaeKYCbqHfRf/CVs5c/VojgA6EyK1n fEq/Em4/sLa5ND2WErN7mmnmOCwdVm2TU3WFYfLVsZ5NUlriM2HLP2Va2CumYUAT XRRlYljO4= X-Sasl-enc: 8ae3GBgoDZCXVPKVOYbBhSt7QfOG8b/KBg1QzVf+4jxV 1437989686 From: Dima Kogan To: zsh-workers@zsh.org Subject: zargs parallelization support blows up with |& Date: Mon, 27 Jul 2015 02:36:36 -0700 Message-ID: <87lhe23psr.fsf@secretsauce.net> MIME-Version: 1.0 Content-Type: text/plain Hi. I can use this to invoke a perl script 10 times, 2 processes at a time: zargs -P2 -i -l1 `seq 10` -- perl -e 'sleep 20' {} This works ok. However, when I do the same thing, but filter stdout and stderr for some output, then ALL the processes are invoked at the same time, not just 2 at a time like I asked: zargs -P2 -i -l1 `seq 10` -- perl -e 'sleep 20' {} |& grep x I don't know if this is a bug or an expected consequence of some internal implementation details, but this is a really nasty failure mode. Thanks for looking. dima