CODEWITHSUNDEEP
bashgrepag
Chad D
Chad D

Reputation: 319

Is there a better way to grep than using these four commands thrown together?

Essentially what I'm trying to do is parse through some files on my system and pull out a few different things from each file. Here is how I'm currently doing this:

grep -oP "((?<=set_kb_item\(name:)(.*?)(?=, value:))" *.nasl >> /tmp/set_kb_items.txt && 
grep -oP "((?<=user = )(.*?)(?=;))" *.nasl >> /tmp/usernames.txt && 
grep -oP "((?<=dependencies\()(.*?)(?=\)))" *.nasl>> /tmp/dependencies.txt && 
grep -oP "((?<=script_set_attribute\(attribute:\"plugin_type\", value:)(.*?)(?=\)))" *.nasl >> /tmp/plugin_type.txt && 
grep -oP "((?<=script_require_ports\()(.*?)(?=\)))" *.nasl >> /tmp/required_ports.txt

This works perfect for me, and it finishes in about two minutes (70k files). However, I'm curious if I can chain these together a different way? My end goal here is to take this string, and do the equivalent in python, and then send these values to a database, but I'm not quite there yet. Any input would be appreciated, thanks!

Upvotes: 0

Views: 61

Answers (1)

g24l
g24l

Reputation: 3145

What about not chaining them, since there are no dependencies.

grep _yourstaff_ *.nasl >> _youfile1_ & grep _youotherstaff_ *.nasl &

these will be executed as different processes in parallel .

Upvotes: 1

Related Questions