Not as written if you want the 2nd and 3rd grep to have been parallelized.
As written, only the 1st zgrep will be.
Try this instead:
parallel ‘zgrep foo {} | grep bar | grep 192.168.1.100’ ::: 201612*.gz
From: Parallel [mailto:[email protected]] On Behalf Of
Asif Iqbal
On Thu, Apr 20, 2017 at 11:45 AM, Cook, Malcolm wrote:
> Not as written if you want the 2nd and 3rd grep to have been parallelized.
>
>
>
> As written, only the 1st zgrep will be.
>
>
>
> Try this instead:
>
>
>
> parallel ‘zgrep foo {} | grep bar | grep 192.168.1.100’ ::: 201612*.gz
>
right ma
Hi – redirect output as normal:
parallel ‘zgrep foo {} | grep bar | grep 192.168.1.100’ ::: 201612*.gz >
grep_hits.txt
From: Asif Iqbal [mailto:[email protected]]
Sent: Thursday, April 20, 2017 11:30 AM
To: Cook, Malcolm
Cc: [email protected]
Subject: Re: output of parallel pipe to another grep
Oh – you might want to include the –keep-order option as well so your results
come back in file input order.
From: Parallel [mailto:[email protected]] On Behalf Of
Cook, Malcolm
Sent: Thursday, April 20, 2017 11:39 AM
To: 'Asif Iqbal'
Cc: '[email protected]'
Subject: RE:
On Thu, Apr 20, 2017 at 3:24 AM, Asif Iqbal wrote:
> Hi I have multiple compressed files that I need to run grep against.
>
> I am trying to find 'foo', 'bar' and '192.168.1.100' against all the
> compressed log files.
>
> This will work?
>
> ls 201612*.gz | parallel zgrep foo {} | grep bar | grep
Ugh. Typo. Sorry.
parallel --workdir . -S : file ::: *.mp4
Doesn't work because of a mystery issue with the 'file' command
parallel --workdir . -S : basename ::: *.mp4 Works great.
Works great.
- Eric
