CODEWITHSUNDEEP
bashshellfind
hoyhoy
hoyhoy

Reputation: 6351

How do I use a pipe in the exec parameter for a find command?

I'm trying to construct a find command to process a bunch of files in a directory using two different executables. Unfortunately, -exec on find doesn't allow to use pipe or even \| because the shell interprets that character first.

Here is specifically what I'm trying to do (which doesn't work because pipe ends the find command):

find /path/to/jpgs -type f -exec jhead -v {} | grep 123 \; -print

Upvotes: 82

Views: 52382

Answers (6)

linuxgeek
linuxgeek

Reputation: 79

There is kind of another way you can do it but it is also pretty ghetto.

Using the shell option extquote you can do something similar to this in order to make find exec stuff and then pipe it to sh.

root@ifrit findtest # find -type f -exec echo ls $"|" cat \;|sh
filename



root@ifrit findtest # find -type f -exec echo ls $"|" cat $"|" xargs cat\;|sh
h

I just figured I'd add that because at least the way i visualized it, it was closer to the OP's original question of using pipes within exec.

Upvotes: 0

Dimitar
Dimitar

Reputation: 41

Using find command for this type of a task is maybe not the best alternative. I use the following command frequently to find files that contain the requested information:

for i in dist/*.jar; do echo ">> $i"; jar -tf "$i" | grep BeanException; done

Upvotes: 3

Martin Marconcini
Martin Marconcini

Reputation: 27236

Try this

find /path/to/jpgs -type f -exec sh -c 'jhead -v {} | grep 123' \; -print

Alternatively you could try to embed your exec statement inside a sh script and then do:

find -exec some_script {} \;

Upvotes: 90

mweerden
mweerden

Reputation: 14051

With -exec you can only run a single executable with some arguments, not arbitrary shell commands. To circumvent this, you can use sh -c '<shell command>'.

Do note that the use of -exec is quite inefficient. For each file that is found, the command has to be executed again. It would be more efficient if you can avoid this. (For example, by moving the grep outside the -exec or piping the results of find to xargs as suggested by Palmin.)

Upvotes: 4

Palmin
Palmin

Reputation: 2811

A slightly different approach would be to use xargs:

find /path/to/jpgs -type f -print0 | xargs -0 jhead -v | grep 123

which I always found a bit easier to understand and to adapt (the -print0 and -0 arguments are necessary to cope with filenames containing blanks)

This might (not tested) be more effective than using -exec because it will pipe the list of files to xargs and xargs makes sure that the jhead commandline does not get too long.

Upvotes: 16

Xetius
Xetius

Reputation: 46794

As this outputs a list would you not :

find /path/to/jpgs -type f -exec jhead -v {} \; | grep 123

or 

find /path/to/jpgs -type f -print -exec jhead -v {} \; | grep 123

Put your grep on the results of the find -exec.

Upvotes: 1

Related Questions