I haven't used this in a while, but I recall getting errors because this usage of find also 'finds' directories, binaries, and just about everything else under the sun. Because it finds binaries, directories, etc. it attempts to search them and gets pretty messy.
Will find only regular files, and not directories, but does not stop the grep from searching large binaries, as I recall. That is why I usually don't use this combo for grepping strings and forgot about this one. I don't recall a switch in find to stop it from 'finding' binary files. Perhaps there is ?
Folks;
First about find:
when i run this:
find . -name '*log*' -mtime +10 -print | sed 's+^\./++;s+/.*++' | sort -u
i got list of log files but also get a directories (although directory names doesn't have "log" in it).
How can i exclude the directory from the output of this find command? ... (2 Replies)
find . -type f -name "*.sql" -print|xargs perl -i -pe 's/pattern/replaced/g'
this is simple logic to find and replace in multiple files & folders
Hope this helps.
Thanks
Zaheer (0 Replies)
Hi All,
Please i need to know the difference between grep, egrep & grep -i when used to serach through a file.
My platform is SunOS 5.9 & i'm using the korn shell.
Regards,
- divroro12 - (2 Replies)
Hi All,
Please tell me how can I Find a string using grep & print the line above or below that in solaris?
Please share as I am unable to use grep -A or grep -B as it is not working on Solaris. (10 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)
Hello people!
I would like to create one script following this stage
I have one directory with 100 files
File001
File002
...
File100
(This is the format of content of the 100 files)
2012/03/10 12:56:50:221875936 1292800448912 12345 0x00 0x04 0
then I have one... (0 Replies)
I am making an eBook.
I am editing the html in BBedit.
I need to replace all <p class="s5"> with just a <p>.
How do I write this for GREP?
Thank you,
Abby (5 Replies)
Guys,
i've got hundreds of C programs in my ~/devel/ directory and sub-directories. is there a way i can use grep -r followed by some zsh, sh, bash, to find some code that starts with "&foo" or something similar?
thanks in advance! (9 Replies)
In COBOL, a hyphen can be used in a field name and in a specific program some field names would be identical to others except a suffix was added--sometimes a suffix to a suffix was used. For example, assume I am looking for AAA, AAA-BBB, and AAA-BBB-CCC and don't want to look at AAA-BBB-CCC... (7 Replies)
Discussion started by: wbport
7 Replies
LEARN ABOUT FREEBSD
whereis
WHEREIS(1) BSD General Commands Manual WHEREIS(1)NAME
whereis -- locate programs
SYNOPSIS
whereis [-abmqsux] [-BMS dir ... -f] program ...
DESCRIPTION
The whereis utility checks the standard binary, manual page, and source directories for the specified programs, printing out the paths of any
it finds. The supplied program names are first stripped of leading path name components, any single trailing extension added by gzip(1),
compress(1), or bzip2(1), and the leading 's.' or trailing ',v' from a source code control system.
The default path searched is the string returned by the sysctl(8) utility for the ``user.cs_path'' string, with /usr/libexec and the current
user's $PATH appended. Manual pages are searched by default along the $MANPATH. Program sources are located in a list of known standard
places, including all the subdirectories of /usr/src and /usr/ports.
The following options are available:
-B Specify directories to search for binaries. Requires the -f option.
-M Specify directories to search for manual pages. Requires the -f option.
-S Specify directories to search for program sources. Requires the -f option.
-a Report all matches instead of only the first of each requested type.
-b Search for binaries.
-f Delimits the list of directories after the -B, -M, or -S options, and indicates the beginning of the program list.
-m Search for manual pages.
-q (``quiet''). Suppress the output of the utility name in front of the normal output line. This can become handy for use in a back-
quote substitution of a shell command line, see EXAMPLES.
-s Search for source directories.
-u Search for ``unusual'' entries. A file is said to be unusual if it does not have at least one entry of each requested type. Only
the name of the unusual entry is printed.
-x Do not use ``expensive'' tools when searching for source directories. Normally, after unsuccessfully searching all the first-level
subdirectories of the source directory list, whereis will ask locate(1) to find the entry on its behalf. Since this can take much
longer, it can be turned off with -x.
EXAMPLES
The following finds all utilities under /usr/bin that do not have documentation:
whereis -m -u /usr/bin/*
Change to the source code directory of ls(1):
cd `whereis -sq ls`
SEE ALSO find(1), locate(1), man(1), which(1), sysctl(8)HISTORY
The whereis utility appeared in 3.0BSD. This version re-implements the historical functionality that was lost in 4.4BSD.
AUTHORS
This implementation of the whereis command was written by Jorg Wunsch.
BUGS
This re-implementation of the whereis utility is not bug-for-bug compatible with historical versions. It is believed to be compatible with
the version that was shipping with FreeBSD 2.2 through FreeBSD 4.5 though.
The whereis utility can report some unrelated source entries when the -a option is specified.
BSD August 22, 2002 BSD