Recursive grep Post: 302196481

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

grep recursive directories

I am trying to locate a file or files with specific data in them. Problem is the file(s) could reside in any one of many directories. My question is. Is there a way of recursively greping directories for the file(s) with the data I am looking for. I have tried - 1. $HOME> grep 47518 | ls...

2. UNIX for Dummies Questions & Answers

recursive GREP ?

Hi! Suppose I have a directory (no symbolic links) called /WORK that contains 3 subdirectories: /A /B /C My problem is this: I want to look for a file that contains an order number. So far, I obtain what I want by doing this /home/acb% cd /WORK/A /home/acb/WORK/A% grep '093023553' *.*...

3. UNIX for Dummies Questions & Answers

recursive grep output

I'm using this command to get a recursive grep find . -name *.i -exec grep 'blah blah' {} \; -exec ls {} \; now I would like to obtain just the list of the files and not also the line of the file. How should I change the syntax? thank you,

4. Shell Programming and Scripting

Preventing an endless loop with recursive grep

When finding a string in files within a directory, one can use this: grep -r "searchstring" dir/subdir/ > listofoccurrences.txt For brevity sake one can enter the intended directory and use this: grep -r "searchstring" . > listofoccurrences.txt which as I found out leads to an endless loop,...

5. UNIX for Advanced & Expert Users

recursive grep

Hi, on AIX 6.1 , in man document for grep : -r Searches directories recursively. By default, links to directories are followed. But when I use : oracle@XXX:/appli/XXX_SCRIPTS#grep -r subject *.sh It returns nothing. However I have at least one row in a file : ...

6. Shell Programming and Scripting

Tricky recursive removal (find with grep)

Tricky one: I want to do several things all at once to blow away a directory (rm -rf <dir>) 1) I want to find all files recursively that have a specific file extension (.ver) for example. 2) Then in that file, I want to grep for an expression ( "sp2" ) for example. 3) Then I want to...

7. Shell Programming and Scripting

Recursive Grep with replace

I have seen some useful infomation about recursive grep in one of the thread. Can it is possible to combine resursive grep and replace togather? Means I need to replace old server names in all the files with new server names as we are upgrading our applications. There are lots of files in...

8. Shell Programming and Scripting

Recursive find / grep within a file / count of a string

Hi All, This is the first time I have posted to this forum so please bear with me. Thanks also advance for any help or guidance. For a project I need to do the following. 1. There are multiple files in multiple locations so I need to find them and the location. So I had planned to use...

9. UNIX for Advanced & Expert Users

Recursive grep with only certain types of files

Can I please have some ideas on how to do a recursive grep with certain types of files? The file types I want to use are *.c and *.java. I know this normally works with all files. grep -riI 'scanner' /home/bob/ 2>/dev/null Just not sure how to get it to work *.c and *.java files.

LEARN ABOUT REDHAT

pcregrep

PCREGREP(1)						      General Commands Manual						       PCREGREP(1)

NAME

       pcregrep - a grep with Perl-compatible regular expressions.

SYNOPSIS

       pcregrep [-Vcfhilnrsvx] pattern [file] ...

DESCRIPTION

       pcregrep  searches files for character patterns, in the same way as other grep commands do, but it uses the PCRE regular expression library
       to support patterns that are compatible with the regular expressions of Perl 5. See pcre(3) for a full description of syntax and semantics.

       If no files are specified, pcregrep reads the standard input. By default, each line that matches the pattern is copied to the standard out-
       put,  and  if  there is more than one file, the file name is printed before each line of output. However, there are options that can change
       how pcregrep behaves.

       Lines are limited to BUFSIZ characters. BUFSIZ is defined in <stdio.h>.	The newline character is removed from the end of each line  before
       it is matched against the pattern.

OPTIONS

       -V	 Write the version number of the PCRE library being used to the standard error stream.

       -c	 Do  not print individual lines; instead just print a count of the number of lines that would otherwise have been printed. If sev-
		 eral files are given, a count is printed for each of them.

       -ffilename
		 Read patterns from the file, one per line, and match all patterns against each line. There is a maximum of 100 patterns. Trailing
		 white space is removed, and blank lines are ignored. An empty file contains no patterns and therefore matches nothing.

       -h	 Suppress printing of filenames when searching multiple files.

       -i	 Ignore upper/lower case distinctions during comparisons.

       -l	 Instead  of  printing lines from the files, just print the names of the files containing lines that would have been printed. Each
		 file name is printed once, on a separate line.

       -n	 Precede each line by its line number in the file.

       -r	 If any file is a directory, recursively scan the files it contains. Without -r a directory is scanned as a normal file.

       -s	 Work silently, that is, display nothing except error messages.  The exit status indicates whether any matches were found.

       -v	 Invert the sense of the match, so that lines which do not match the pattern are now the ones that are found.

       -x	 Force the pattern to be anchored (it must start matching at the beginning of the line) and in addition, require it to	match  the
		 entire  line.	This  is  equivalent  to  having ^ and $ characters at the start and end of each alternative branch in the regular
		 expression.

SEE ALSO

       pcre(3), Perl 5 documentation

DIAGNOSTICS

       Exit status is 0 if any matches were found, 1 if no matches were found, and 2 for syntax errors or inacessible files (even if matches  were
       found).

AUTHOR

       Philip Hazel <ph10@cam.ac.uk>

       Last updated: 15 August 2001
       Copyright (c) 1997-2001 University of Cambridge.

																       PCREGREP(1)