recursive GREP ? Post: 39545

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

Hello, First time post - I have no formal unix training and could use some help with this. I have a list of strings in File1 that I want to use to do a recursive search (grep) under a specific directory. Here is an example of the string I need to search: /directory/dire...

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 OPENSOLARIS

fgrep

fgrep(1)							   User Commands							  fgrep(1)

NAME

       fgrep - search a file for a fixed-character string

SYNOPSIS

       /usr/bin/fgrep [-bchilnsvx] -e pattern_list [file...]

       /usr/bin/fgrep [-bchilnsvx] -f file [file...]

       /usr/bin/fgrep [-bchilnsvx] pattern [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] -e pattern_list [-f file]
	    [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] [-e pattern_list] -f file
	    [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] pattern [file...]

DESCRIPTION

       The  fgrep (fast grep) utility searches files for a character string and prints all lines that contain that string. fgrep is different from
       grep(1) and from egrep(1) because it searches for a string, instead of searching for a pattern that matches an  expression.  fgrep  uses  a
       fast and compact algorithm.

       The characters $, *, [, ^, |, (, ), and  are interpreted literally by fgrep, that is, fgrep does not recognize full regular expressions as
       does egrep. These characters have special meaning to the shell. Therefore, to be safe, enclose the entire string within single quotes (a').

       If no files are specified, fgrep assumes standard input. Normally, each line that is found is copied to the standard output. The file  name
       is printed before each line that is found if there is more than one input file.

OPTIONS

       The following options are supported for both /usr/bin/fgrep and /usr/xpg4/bin/fgrep:

       -b		  Precedes each line by the block number on which the line was found. This can be useful in locating block numbers by con-
			  text. The first block is 0.

       -c		  Prints only a count of the lines that contain the pattern.

       -e pattern_list	  Searches for a string in pattern-list. This is useful when the string begins with a -.

       -f pattern-file	  Takes the list of patterns from pattern-file.

       -h		  Suppresses printing of files when searching multiple files.

       -i		  Ignores upper/lower case distinction during comparisons.

       -l		  Prints the names of files with matching lines once, separated by new-lines. Does not repeat the names of files when  the
			  pattern is found more than once.

       -n		  Precedes each line by its line number in the file. The first line is 1.

       -s		  Works silently, that is, displays nothing except error messages. This is useful for checking the error status.

       -v		  Prints all lines except those that contain the pattern.

       -x		  Prints only lines that are matched entirely.

   /usr/xpg4/bin/fgrep
       The following options are supported for /usr/xpg4/bin/fgrep only:

       -q    Quiet.  Does  not	write  anything  to  the standard output, regardless of matching lines. Exits with zero status if an input line is
	     selected.

OPERANDS

       The following operands are supported:

       file    Specifies a path name of a file to be searched for the patterns. If no file operands are specified,  the  standard  input  will	be
	       used.

   /usr/bin/fgrep
       pattern	  Specifies a pattern to be used during the search for input.

   /usr/xpg4/bin/fgrep
       pattern	  Specifies  one  or  more  patterns to be used during the search for input. This operand is treated as if it were specified as -e
		  pattern_list.

USAGE

       See largefile(5) for the description of the behavior of fgrep when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).

ENVIRONMENT VARIABLES

       See environ(5) for descriptions of the following environment variables that affect the execution of fgrep:  LC_COLLATE,	LC_CTYPE,  LC_MES-
       SAGES, and NLSPATH.

EXIT STATUS

       The following exit values are returned:

       0    If any matches are found

       1    If no matches are found

       2    For syntax errors or inaccessible files, even if matches were found.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

   /usr/bin/fgrep
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

   /usr/xpg4/bin/fgrep
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWxcu4			   |
       +-----------------------------+-----------------------------+
       |CSI			     |Enabled			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       ed(1), egrep(1), grep(1), sed(1), sh(1), attributes(5), environ(5), largefile(5), XPG4(5)

NOTES

       Ideally, there should be only one grep command, but there is not a single algorithm that spans a wide enough range of space-time tradeoffs.

       Lines are limited only by the size of the available virtual memory.

   /usr/xpg4/bin/fgrep
       The  /usr/xpg4/bin/fgrep  utility  is identical to /usr/xpg4/bin/grep -F (see grep(1)). Portable applications should use /usr/xpg4/bin/grep
       -F.

SunOS 5.11							    24 Mar 2006 							  fgrep(1)