Using parallel -u --results -j 3 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 redirec
On Thu, Feb 27, 2014 at 11:06 PM, Rob Sargent wrote:
> Using parallel -u --results -j 3 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...)
>
> I
Wonderful. I had only tried escaping it with backslash. My apologies.
rjs
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 myApp -a {}> /dev/null 2>&1 ::: a1 a2
a3 a4 appears to be working. All three stdouts are b
On Fri, Feb 28, 2014 at 1:58 AM, Ole Tange wrote:
> On Thu, Feb 27, 2014 at 11:06 PM, Rob Sargent wrote:
:
>> 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:
>
>
