topic Re: grep recursive in Operating System - Linux

grep recursive

Francesco_13 — Fri, 15 Sep 2006 03:51:32 GMT

Hi,

how i can find the word "force" in all text file of my hp-ux system?
grep -i force * find in executables file too..

thanks

Best regards.
Francesco

Re: grep recursive

IT_2007 — Fri, 15 Sep 2006 03:57:57 GMT

you won't be able to find word from executables using grep command. you have to use strings first and then use grep command to find the words.

Re: grep recursive

IT_2007 — Fri, 15 Sep 2006 03:59:04 GMT

like

strings /etc/lvmtab |grep "vg"

which will show you only names with vg.

Re: grep recursive

Francesco_13 — Fri, 15 Sep 2006 04:05:34 GMT

Hi,
i wolud find recursively where i have the word 'force' in all my files in the system...

with you suggested command i can do it this?

thanks and regards

Re: grep recursive

Pete Randall — Fri, 15 Sep 2006 05:21:08 GMT

Use the find command in conjunction with grep:

find /start_dir -type f -exec grep -l "force" {} \;

Be warned, however, that binary files will do not grep well. Ideally you would need to find some way to exclude binaries, perhaps by being more selective about which directories you "find" in.

Pete

Re: grep recursive

Francesco_13 — Fri, 15 Sep 2006 05:54:27 GMT

thanks to all.
Question solved.

regards.
Francesco

Re: grep recursive

James R. Ferguson — Fri, 15 Sep 2006 06:00:04 GMT

Hi:

Using '-exec' with 'find' causes a separate process to be forked for every file found. This can be very detrimental to your system's performance.

Secondly, you should add '-xdev' so that you do not cross mountpoints as 'find' descends directories. This would be *very* important if you were interested in searching the root 'root' filesystem (including '/etc' which is not a separate mountpoint but excluding trees like '/usr' and '/opt' which are there own mountpoints.

Thus, at a minimum, do:

# find /path -xdev -type f | xargs grep -i force

Regards!

...JRF...

Re: grep recursive

Peter Godron — Fri, 15 Sep 2006 06:06:21 GMT

Francesco,
variation on a theme:
grep force `find / -exec file {} \; | grep -v directory | grep -v executable | awk -F':' '{print $1}'`

This should exclude directories and execuatble as defined by file (man file)

Re: grep recursive

James R. Ferguson — Fri, 15 Sep 2006 07:14:46 GMT

Hi (again) Francesco:

[ It's taken an hour to be able to post this...the Forum has been out-to-lunch ]

If you want to be able to restrict your 'grep' to only text files ( and not binary ones ) and in addition identify each file matching the pattern you specify, use:

# cat ./google
#!/usr/bin/sh
typeset DIR=$1
typeset PAT=$2
find ${DIR} -xdev -type f | while read FILE
do
[ `file ${FILE} | grep -c ascii` -eq 0 ] && continue
grep "$PAT" ${FILE} /dev/null
done
exit 0

...run as:

# ./google /path pattern

for example:

# ./google /etc hostname

Regards!

...JRF...

Re: grep recursive

Francesco_13 — Fri, 15 Sep 2006 07:19:09 GMT

Hi,
thanks to reply. Due a delay of forum i cannot submit points(the therad was closed..) ..i would 10 point for you!

Best regards.
Francesco

Re: grep recursive

Pete Randall — Fri, 15 Sep 2006 07:22:48 GMT

Francesco,

You can still assign JRF the points he deserves. Click on the "reopen thread" button, then assign the points, then click on the "close thread" button.

Pete

Re: grep recursive

IT_2007 — Fri, 15 Sep 2006 08:15:17 GMT

Francesco,

Thread is not closed. Please assign points to JRF. He deserves it.

Thanks,
IT_2007

Re: grep recursive

Francesco_13 — Mon, 18 Sep 2006 01:26:10 GMT

Hi,
ok, before weekend was be problematic connect with forum. This morning it's ok! assigned points.
we can close the thread.
thanks to all
regards.
Francesco

Re: grep recursive

Francesco_13 — Mon, 18 Sep 2006 02:48:22 GMT

Hi,
when i run the script from / of my hp-ux, after several minutes i receive this error:
/usr/bin/grep: The parameter list is too long.
I donÂ´t know where have stopped.

i use:
grep -i force `find / -exec file {} \; | grep -v directory | grep -v executable | awk -F':' '
{print $1}'`

How i can remove this problem?

Thanks.

Best regards.

Francesco

Re: grep recursive

Francesco_13 — Mon, 18 Sep 2006 03:08:52 GMT

Hi,

for the other option with:
#!/usr/bin/sh
typeset DIR=$1
typeset PAT=$2
find ${DIR} -xdev -type f | while read FILE
do
[ `file ${FILE} | grep -ic ascii` -eq 0 ] && continue
grep "$PAT" ${FILE} /dev/null
done
exit

I have introduced -i option for uppercase. But one question: how i can do it for find only word "force" and no returning me other words how for example "forced" where force it's present?

Thanks.

Best regards.
Francesco

Re: grep recursive

James R. Ferguson — Mon, 18 Sep 2006 05:23:20 GMT

Hi (again) Francesco:

A simple 'grep' will match the string of characters without regard to where they occur. A simple solution for finding only the word "force" would be:

# grep -i -e "^force " -e " force$" -e " force "

The caret (^) anchors the string to the beginning of a line. The dollar sign ($) anchors the string at the line's end. Surrounding the string with spaaces " " creates the sense of an English word.

In answer to your question regarding Peter's script, the "parameter list is too long" error arises because the 'find' is creating a list of files for input the 'grep'. The list generated is too long to be passed to 'grep' in one unit.

Regards!

...JRF...

Re: grep recursive

Dennis Handly — Sun, 30 Oct 2011 02:10:44 GMT

>grep -i force `find / -exec file {} \; | grep -v directory | grep -v executable | awk -F':' '
{print $1}'`

Peter's script is not the proper way to use find, if it will return an infinite number of files. You must use xargs or better yet use -exec grep +.

It seems you can only use -exec file +. But you shouldn't use `find ...`.

You need to replace by:

find / -exec file + | \
grep -v -e directory -e executable | \
awk -F":" '{print $1}' | xargs -n40 grep -i force

You may want to add 2> /dev/null to the find and the last grep.

>how i can do it for find only word "force" and no returning me other words how for example "forced" where force it's present?

You need to use grep -w. (If you are on 11.11) This is easier than James' solution. Otherwise a more rigorous solution for 11.00 would use

[[:space:][:punct:]] where he has a blank, before and after your word "force".