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 <[email protected]>
Cc: [email protected]
Subject: Re: output of parallel pipe to another grep
On Thu, Apr 20, 2017 at 11:45 AM, Cook, Malcolm
<[email protected]<mailto:[email protected]>> 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 make sense, How do I redirect the output to a file?
From: Parallel
[mailto:parallel-bounces+mec<mailto:parallel-bounces%2Bmec>[email protected]<mailto:[email protected]>]
On Behalf Of Asif Iqbal
Sent: Wednesday, April 19, 2017 8:24 PM
To: [email protected]<mailto:[email protected]>
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<http://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<http://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?
