Performing a non-recursive find in Unix


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Performing a non-recursive find in Unix
Prev   Next
# 1  
Old 09-05-2002
Question Performing a non-recursive find in Unix

I need to perform a non-recursive find in Unix. Sounds simple, but it doesn't actually work. The command ALWAYS searches through the subdirectories.

Any ideas? I am on DEC Unix :-(
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Recursive Find on file size

Is there a way to use the find command to recursively scan directories for files greater than 1Gb in size and print out the directory path and file name only? Thanks in advance. (6 Replies)
Discussion started by: jimbojames
6 Replies

2. UNIX for Dummies Questions & Answers

Non Recursive Find Command

Hello Unix Gurus, I am using the following find commands: 1) find Input_Path -name '*.' -exec mv -f {} Outputpath \; 2) find Inputpath -name '*.' -exec cp {} Outputpath \; 3) find Somepath -name '*.' Now the problem is my Unix version does not support maxdepth Option for find... (7 Replies)
Discussion started by: pchegoor
7 Replies

3. UNIX for Dummies Questions & Answers

Some advice please on non-recursive find

Hi all, I am currently writing a find-and-remove kind of script that is to be used for Solaris and Linux. Currently am using the find command below that I is in find only current directory (universal) | commandlinefu.com This however gives me the "ksh: /bin/find: arg list too long" error... (6 Replies)
Discussion started by: newbie_01
6 Replies

4. Shell Programming and Scripting

How to find the latest file on Unix or Linux (recursive)

Hi all, I need to get the latest file. I have found this command "ls -lrt" that is great but not recursive. Can anyone help? Thanx by advance. (7 Replies)
Discussion started by: 1or2is3
7 Replies

5. UNIX for Advanced & Expert Users

Non recursive find command

Hi, I have question is related to find command. I want to find command should search in current folder only not recursive mode(sub-folders). I found a one way of, find . \( -name success -prune \) -o -name "Rajini*" How ever, my current folder is having lots sub-folders and am not... (7 Replies)
Discussion started by: Nagapandi
7 Replies

6. Shell Programming and Scripting

Recursive find and store

I HAVE A TEXT FILE CONTAINING THE VALUES 1.CPP 2.CPP 3.CPP 4.CPP 5.CPP 6.CPP I WANT TO TAKE EACH .CPP AND USE THE FIND COMMAND TO FIND THE LATEST VERSION OF THE FOLDER IN WHICH IT IS PRESENT. HOW DO I IMPLEMENT IT IN A WHILE LOOP I TRIED SOMETHING LIKE THIS WHILE CAT... (3 Replies)
Discussion started by: ultimatix
3 Replies

7. UNIX for Advanced & Expert Users

identify the unix process performing high disk i/o reads and writes

Guys, Is there any UNIX command that captures the 'Unix process which is performing high disk I/O reads and writes'. can you help me in this? -Swamy (6 Replies)
Discussion started by: avsswamy
6 Replies

8. Shell Programming and Scripting

identify the unix processes performing high disk i/o reads and writes

I would like to write shell/perl script which identifies the top unix processes that are performing high disk I/O's or/and writes If any one knows the solution please help me? -Swamy (0 Replies)
Discussion started by: avsswamy
0 Replies

9. UNIX for Dummies Questions & Answers

making a recursive find more useful..

Hi everyone, I'm using a recursive find (you know the type, find . -name qwert*) to find a set of files. However, because I'm new to the system and there is not much documentation about these particular files I'm trying to find them using this recursive find. I started off at the location... (3 Replies)
Discussion started by: spanish_tony
3 Replies

10. UNIX for Dummies Questions & Answers

Question: non-recursive find syntax

Hello, I am trying to search a directory for all files matching "G*" without looking in sub-directories "success" and "error". I've searched this forum and found the following syntax, but can't make it work: find . \( ! -name success -prune -name error -prune \) -type f -name "G*" Have... (6 Replies)
Discussion started by: alexkav
6 Replies
Login or Register to Ask a Question
glob(n) 						       Tcl Built-In Commands							   glob(n)

__________________________________________________________________________________________________________________________________________________

NAME
glob - Return names of files that match patterns SYNOPSIS
glob ?switches? pattern ?pattern ...? _________________________________________________________________ DESCRIPTION
This command performs file name ``globbing'' in a fashion similar to the csh shell. It returns a list of the files whose names match any of the pattern arguments. If the initial arguments to glob start with - then they are treated as switches. The following switches are currently supported: | -directory directory | Search for files which match the given patterns starting in the given directory. This allows searching of directories whose name | contains glob-sensitive characters without the need to quote such characters explicitly. This option may not be used in conjunction | with -path, which is used to allow searching for complete file paths whose names may contain glob-sensitive characters. | -join | The remaining pattern arguments are treated as a single pattern obtained by joining the arguments with directory separators. -nocomplain Allows an empty list to be returned without error; without this switch an error is returned if the result list would be empty. | -path pathPrefix | Search for files with the given pathPrefix where the rest of the name matches the given patterns. This allows searching for files | with names similar to a given file (as opposed to a directory) even when the names contain glob-sensitive characters. This option | may not be used in conjunction with -directory. For example, to find all files with the same root name as $path, but differing | extensions, you should use glob -path [file rootname $path] .* which will work even if $path contains numerous glob-sensitive char- | acters. | -tails | Only return the part of each file found which follows the last directory named in any -directory or -path path specification. Thus | glob -tails -directory $dir * is equivalent to set pwd [pwd] ; cd $dir ; glob *; cd $pwd. For -path specifications, the returned | names will include the last path segment, so glob -tails -path [file rootname ~/foo.tex] .* will return paths like foo.aux foo.bib | foo.tex etc. | -types typeList | Only list files or directories which match typeList, where the items in the list have two forms. The first form is like the -type | option of the Unix find command: b (block special file), c (character special file), d (directory), f (plain file), l (symbolic | link), p (named pipe), or s (socket), where multiple types may be specified in the list. Glob will return all files which match at | least one of the types given. | The second form specifies types where all the types given must match. These are r, w, x as file permissions, and readonly, hidden | as special permission cases. On the Macintosh, MacOS types and creators are also supported, where any item which is four characters | long is assumed to be a MacOS type (e.g. TEXT). Items which are of the form {macintosh type XXXX} or {macintosh creator XXXX} will | match types or creators respectively. Unrecognized types, or specifications of multiple MacOS types/creators will signal an error. | The two forms may be mixed, so -types {d f r w} will find all regular files OR directories that have both read AND write permis- | sions. The following are equivalent: | glob -type d * | glob */ | except that the first case doesn't return the trailing ``/'' and is more platform independent. | -- Marks the end of switches. The argument following this one will be treated as a pattern even if it starts with a -. The pattern arguments may contain any of the following special characters: ? Matches any single character. * Matches any sequence of zero or more characters. [chars] Matches any single character in chars. If chars contains a sequence of the form a-b then any character between a and b (inclu- sive) will match. x Matches the character x. {a,b,...} Matches any of the strings a, b, etc. On Unix, as with csh, a ``.'' at the beginning of a file's name or just after a ``/'' must be matched explicitly or with a {} construct, unless the ``-types hidden'' flag is given (since ``.'' at the beginning of a file's name indicates that it is hidden). On other plat- forms, files beginning with a ``.'' are handled no differently to any others, except the special directories ``.'' and ``..'' which must be matched explicitly (this is to avoid a recursive pattern like ``glob -join * * * *'' from recursing up the directory hierarchy as well as down). In addition, all ``/'' characters must be matched explicitly. If the first character in a pattern is ``~'' then it refers to the home directory for the user whose name follows the ``~''. If the ``~'' is followed immediately by ``/'' then the value of the HOME environment variable is used. The glob command differs from csh globbing in two ways. First, it does not sort its result list (use the lsort command if you want the list sorted). Second, glob only returns the names of files that actually exist; in csh no check for existence is made unless a pattern contains a ?, *, or [] construct. PORTABILITY ISSUES
Unlike other Tcl commands that will accept both network and native style names (see the filename manual entry for details on how native and network names are specified), the glob command only accepts native names. Windows For Windows UNC names, the servername and sharename components of the path may not contain ?, *, or [] constructs. On Windows NT, if pattern is of the form ``~username@domain'' it refers to the home directory of the user whose account information resides on the specified NT domain server. Otherwise, user account information is obtained from the local computer. On Windows 95 and 98, glob accepts patterns like ``.../'' and ``..../'' for successively higher up parent directories. Since the backslash character has a special meaning to the glob command, glob patterns containing Windows style path separators need special care. The pattern C:\foo\* is interpreted as C:foo* where f will match the single character f and * will match the single character * and will not be interpreted as a wildcard character. One solution to this problem is to use the Unix style for- ward slash as a path separator. Windows style paths can be converted to Unix style paths with the command file join $path (or file normalize $path in Tcl 8.4). Macintosh When using the options, -directory, -join or -path, glob assumes the directory separator for the entire pattern is the standard ``:''. When not using these options, glob examines each pattern argument and uses ``/'' unless the pattern contains a ``:''. SEE ALSO
file(n) KEYWORDS
exist, file, glob, pattern Tcl 8.3 glob(n)