Hi,
I need to find out a particular pattern from a directory, for example say X.
The X directory contains 10 c files, and it has subdirectory called Y, and Y has 20 c files within it.
Now I have to find out the pattern only from parent directory X not from sub directory Y.
I have... (4 Replies)
Hey, I have a question about using grep and find together to locate all C programs in a directory containing certain words and open the vi editor with each file. I'm not sure how to do this in one command (as in one line). I know find has a "-exec" option that can call vi, but how do you combine... (1 Reply)
HI
what is the difference between find and grep
if I want to find all the files from different directories which contain "ORA" error, and the line number in each file which has ORA error
should I use pipeline ?
thanks
James (3 Replies)
Hey,
I have a Find command like:
find $searchDir -type f
and this returns a list of files under the directory, which is all good, but, I want to filter that search for files that contain the string "people"
I tried something like:
find $searchDir -type f -exec grep "people" '{}'... (2 Replies)
:wall:Hello, Im having trouble using the find and grep combined into one command. I have the following:
find filname* -mmin -60 grep "ERROR" filename
I want to find the "ERROR" text in any file created in the last hour in the current directory. I dont know how to end the command. If I leave... (3 Replies)
I have a file called 'test.txt' that contains alphanumeric charecters.
The file contains the word 'SBE' followed by other alphabets many times. For example, the file will contain: SBE334GH and also will have SBE77Y8I.
When i do grep 'SBE*' test.txt - it outputs the entire file.
Can you... (5 Replies)
Hi all ,
I'm new to unix
I have a checked project , there exists a file called xxx.config .
now my task is to find all the files in the checked out project which references to this xxx.config file.
how do i use grep or find command . (2 Replies)
How can I recursively find all files in a directory and print out the file and first line number of any text blocks that match the below cases?
This would seem to involve find, xargs, *grep, regex, etc.
In summary, I want to find so-called empty "try-catch blocks" that do not contain code... (0 Replies)
Is it possible with find and Grep to search files under a directory and display only files that have multiple occurrence of a string (In AIX)? Anybody has an example code? If not what are the other options?
Thanks in advance. (7 Replies)
Hi,
On AIX,
We have several moveplan.xml files in different folders.
I run:
find /u0/appl_top/ -name moveplan.xml -exec grep -i Passphrase {} \;
And it returns
<name>Custom Identity Keystore Passphrase File</name>
<name>Custom Trust Keystore Passphrase File</name>
... (4 Replies)
Discussion started by: big123456
4 Replies
LEARN ABOUT BSD
re_exec
REGEX(3) Library Functions Manual REGEX(3)NAME
re_comp, re_exec - regular expression handler
SYNOPSIS
char *re_comp(s)
char *s;
re_exec(s)
char *s;
DESCRIPTION
Re_comp compiles a string into an internal form suitable for pattern matching. Re_exec checks the argument string against the last string
passed to re_comp.
Re_comp returns 0 if the string s was compiled successfully; otherwise a string containing an error message is returned. If re_comp is
passed 0 or a null string, it returns without changing the currently compiled regular expression.
Re_exec returns 1 if the string s matches the last compiled regular expression, 0 if the string s failed to match the last compiled regular
expression, and -1 if the compiled regular expression was invalid (indicating an internal error).
The strings passed to both re_comp and re_exec may have trailing or embedded newline characters; they are terminated by nulls. The regular
expressions recognized are described in the manual entry for ed(1), given the above difference.
SEE ALSO ed(1), ex(1), egrep(1), fgrep(1), grep(1)DIAGNOSTICS
Re_exec returns -1 for an internal error.
Re_comp returns one of the following strings if an error occurs:
No previous regular expression,
Regular expression too long,
unmatched (,
missing ],
too many () pairs,
unmatched ).
3rd Berkeley Distribution May 15, 1985 REGEX(3)