An alternate method to include formatting the filename...
Quote:
Originally Posted by DownunderDave
Thanks for that Wabard.
I have just added another option to the find command so I know which file is being 'cat'ed.
Regarding your requirement for the filename to be output, please note the following should handle your full requirements and should be compatible with all U**X flavors... (I've searched for *.c in my example).
Hai I just want to find a file *.txt in particular direcotry and display the file name puls the content. Do someone know hot to do this, thanks.
I try :
find test/ -name '*.txt' | xargs cat
but It does'nt print out the file name, i want something below print out in my screen :
test/1.txt... (4 Replies)
I'm using Imagemagick to create thumbnails for a large directory tree. The only thing I can't see is how to get it to write the thumbnails to a "thumbs" subdirectory!
Either of these two commands from the Imagemagick site does most of the job:
find -name '*.jpg' | xargs -n1 sh -c 'convert $0... (5 Replies)
I am trying to delete files older than 60 days from a folder:
find /myfolder/*.dat -mtime +60 -exec rm {} \;
ERROR - argument list too long: find
I can't just give the folder name, as there are some files that I don't want to delete. So i need to give with the pattern (*.dat). I can... (3 Replies)
hi,
i've been trying to figure this weird error but I cannot seem to know why. I am using below find command:
find . \( ! -name . -prune \) -type f -mtime +365 -print
The above code returns no file because no files are really more then 365 days old. However, when I use xargs, its... (9 Replies)
Guys i want to run a command to list all directories that havn't been modified in over 548 days ( 1.5 yrs ).
Id like to run a script to first print what the command finds ( so i get a list of the files pre move ... i have a script set for this :
find /Path/Of\ Target/Directory/ -type d -mtime... (4 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)
Hi All,
i'm trying to create a tar of all the .txt files i find in my dir . I've used xargs to acheive this but i wanted to do this with exec and looks like it only archives the last file it finds . can some one advice what's wrong here :
find . -type f -name "*.txt" -print0 | xargs -0... (9 Replies)
Hi,
I want to find some files and then search for some lines in it with a particular pattern and then write those lines into a file. To do this I am using something like this from command prompt directly.
cd /mdat/BVG
find -name "stmt.*cl" -newer temp.txt | xargs -i awk '/BVG-/{print}' {} >... (7 Replies)
Hi, I'm new here and this is my first post. I used command line Unix at work for 3 years... about 10 years ago! Now I can't figure out nor hunt down examples of how to do the following:
Say I built a list of file to backup like this:
find ~ -name "*.pdf" -print >> MYPDF.txt
So I am using find... (6 Replies)
Discussion started by: hwilliam777
6 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