RE: output of parallel pipe to another grep

[Cook, Malcolm]

Hi – redirect output as normal:

 

parallel ‘zgrep foo {} | grep bar | grep 192.168.1.100’ ::: 201612*.gz > grep_hits.txt

 

 

From: Asif Iqbal [mailto:vadud3@gmail.com]
Sent: Thursday, April 20, 2017 11:30 AM
To: Cook, Malcolm <MEC@stowers.org>
Cc: parallel@gnu.org
Subject: Re: output of parallel pipe to another grep

 

 

 

On Thu, Apr 20, 2017 at 11:45 AM, Cook, Malcolm <MEC@stowers.org> wrote:

Not as written if you want the 2^nd and 3^rd grep to have been parallelized.

 

As written, only the 1^st zgrep will be.

 

Try this instead:

 

parallel ‘zgrep foo {} | grep bar | grep 192.168.1.100’ ::: 201612*.gz

 

 

right make sense, How do I redirect the output to a file?

 

 

 

 

From: Parallel [mailto:parallel-bounces+mec=stowers.org@gnu.org] On Behalf Of Asif Iqbal
Sent: Wednesday, April 19, 2017 8:24 PM
To: parallel@gnu.org
Subject: output of parallel pipe to another grep

 

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 192.168.1.100 

 

Thanks for such an awsome tool!

 

--

Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

 

--

Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?