[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: limits on stdout

From: Rob Sargent
Subject: Re: limits on stdout
Date: Thu, 27 Feb 2014 18:01:02 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

Wonderful. I had only tried escaping it with backslash. My apologies.

On 02/27/2014 05:58 PM, Ole Tange wrote:
On Thu, Feb 27, 2014 at 11:06 PM, Rob Sargent <> wrote:
Using parallel -u --results -j 3 <dir> myApp -a {}> /dev/null 2>&1 ::: a1 a2
a3 a4 appears to be working.  All three stdouts are being written to
equally.  Thanks. (All three are still running so I haven't confirmed the
redirect yet...)

It appears to me that one cannot use parameters in the redirect e.g ">
path/{}.foo".  Is that correct?
No that is not correct. But the path must exist and the > must be quoted:

     mkdir bar
     parallel echo ">" bar/{}.foo ::: 1 2 3


reply via email to

[Prev in Thread] Current Thread [Next in Thread]