|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
find command
Post 9767 by Perderabo on Friday 2nd of November 2001 09:44:43 AM
11-02-2001
Re: find /tmp -type f -regex .*\/t[^\/]*$ -exec rm {} \;
Quote:
Originally posted by Neo
From here, seems like Perderabo's"
find /tmp \( ! -name /tmp -prune \) -type f -name t\*....
However, This does not work for me either !!!!
From here, seems like Perderabo's"
find /tmp \( ! -name /tmp -prune \) -type f -name t\*....
However, This does not work for me either !!!!
cd /
find tmp \( ! -name tmp -prune \) -type f -name t\*....
This time I tested it. I should know better than to post something like that without testing.
stuff like "rm t*" would seem to address the OP's original question until you notice the "-mtime" in his example.
Another concern is that "rm t*" will work only if there are a small number of files that start with t. Create 20,000 files that start with t in /tmp and now it will blow that max command line size on most versions of unix.
Quote:
Originally posted by Neo
rm -f `find -type f /tmp|grep t*
However, this also has problems because find returns the full path name so the syntax above will not work, seems to me
rm -f `find -type f /tmp|grep t*
However, this also has problems because find returns the full path name so the syntax above will not work, seems to me
rm -f `find /tmp -type f |grep t*`
will sort-of work. "grep t*" is going to match anything with zero or more t's in it, so that's not what we want. Also this will decend into subdirecties which is not what the op wanted.
This is nothing wrong with feeding full path names to rm except that it exacerbates the limited command line problem.
Once we have the find statement, rather than ending it with "-exec rm {} \;", I like "-print | xargs rm" which will fire up only as many rm processes as is needed rather than one per file. If someone does have 20,000 file that start with t, the difference is dramatic.
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I create a file touch 1201093003 fichcomp
and inside a repertory (which hava a lot of files) I want to list all files created before this file :
find *.* \! -maxdepth 1 - newer fichcomp but this command returned bash: /usr/bin/find: Argument list too long
but i make a filter all... (1 Reply)
Discussion started by: yacsil
1 Replies
2. Shell Programming and Scripting
Yes , I have to find a file in unix without using any find or where commands.Any pointers for the same would be very helpful as i am beginner in shell scritping and need a solution for the same.
Thanks in advance.
Regards
Jatin Jain (10 Replies)
Discussion started by: jatin.jain
10 Replies
3. UNIX for Dummies Questions & Answers
I need to find whether there is a file named vijay is there or not in folder named "opt" .I tried "ls *|grep vijay" but it showed permission problem.
so i need to use find command (6 Replies)
Discussion started by: amirthraj_12
6 Replies
4. Shell Programming and Scripting
I am using csh and getting the error "find: No match." but I cannot figure out why. What I am trying to do is set the find command to a variable and then execute the variable as a command. I ran it through a debugger and it looks like $FIND is getting set but the find command can not actually be... (2 Replies)
Discussion started by: mst3k4l
2 Replies
5. Linux
Hi,
I'm using the following command to find the multiple requierd file types and its working fine
find . -name "*.pl" -o -name "*.pm" -o -name "*.sql" -o -name "*.so" -o -name "*.sh" -o -name "*.java" -o -name "*.class" -o -name "*.jar" -o -name "*.gz" -o -name "*.Z" -type f
Though... (2 Replies)
Discussion started by: vickramshetty
2 Replies
6. Shell Programming and Scripting
I want to find a dir called STOP from the root.so what is the find command.
Thanks & Regards
Rajkumar (1 Reply)
Discussion started by: rajkumar_g
1 Replies
7. Shell Programming and Scripting
Hello everyone,
first post here, trying to learn scripting on my own and this forum as been really helpful so far. I made few little scripts working great but I m facing some problems with RE.
I have a bunch of files in many subdirectories called *001.ext *002.ext OR simple *.ext or *01.ext... (7 Replies)
Discussion started by: Sekullos
7 Replies
8. Shell Programming and Scripting
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)
Discussion started by: Gangam
2 Replies
9. Shell Programming and Scripting
Hi,
I want find multiple string in one file using find coomand.
And keeping it in one variable.grep is not working. (5 Replies)
Discussion started by: vivek1489
5 Replies
10. Solaris
Hello,
I am running some performance based tests on Solaris, and I was wondering how fast the "seeking" rate of Solaris is, or how fast Solaris can get information about files with the "find" command. Does anyone know what 'find' command I could run to traverse through my system to see the rate... (1 Reply)
Discussion started by: bstring
1 Replies
LEARN ABOUT MOJAVE
dh_install
DH_INSTALL(1) Debhelper DH_INSTALL(1) NAME
dh_install - install files into package build directories SYNOPSIS
dh_install [-Xitem] [--autodest] [--sourcedir=dir] [debhelperoptions] [file|dir...destdir] DESCRIPTION
dh_install is a debhelper program that handles installing files into package build directories. There are many dh_install* commands that handle installing specific types of files such as documentation, examples, man pages, and so on, and they should be used when possible as they often have extra intelligence for those particular tasks. dh_install, then, is useful for installing everything else, for which no particular intelligence is needed. It is a replacement for the old dh_movefiles command. This program may be used in one of two ways. If you just have a file or two that the upstream Makefile does not install for you, you can run dh_install on them to move them into place. On the other hand, maybe you have a large package that builds multiple binary packages. You can use the upstream Makefile to install it all into debian/tmp, and then use dh_install to copy directories and files from there into the proper package build directories. From debhelper compatibility level 7 on, dh_install will fall back to looking in debian/tmp for files, if it does not find them in the current directory (or wherever you've told it to look using --sourcedir). FILES
debian/package.install List the files to install into each package and the directory they should be installed to. The format is a set of lines, where each line lists a file or files to install, and at the end of the line tells the directory it should be installed in. The name of the files (or directories) to install should be given relative to the current directory, while the installation directory is given relative to the package build directory. You may use wildcards in the names of the files to install. Note that if you list exactly one filename or wildcard-pattern on a line by itself, with no explicit destination, then dh_install will automatically guess the destination to use, the same as if the --autodest option were used. debian/not-installed Used with the deprecated --list-missing and --fail-missing options. Please refer to dh_missing(1) for the documentation of this file. OPTIONS
--list-missing Deprecated: Please use dh_missing --list-missing instead. If you use this option, dh_install will call dh_missing with that option after it has processed all the files. Please see dh_missing(1) for the documentation of this option. This option is removed in compat 12. --fail-missing Deprecated: Please use dh_missing --fail-missing instead. If you use this option, dh_install will call dh_missing with that option after it has processed all the files. Please see dh_missing(1) for the documentation of this option. This option is removed in compat 12. --sourcedir=dir Look in the specified directory for files to be installed. Note that this is not the same as the --sourcedirectory option used by the dh_auto_* commands. You rarely need to use this option, since dh_install automatically looks for files in debian/tmp in debhelper compatibility level 7 and above. --autodest Guess as the destination directory to install things to. If this is specified, you should not list destination directories in debian/package.install files or on the command line. Instead, dh_install will guess as follows: Strip off debian/tmp (or the sourcedir if one is given) from the front of the filename, if it is present, and install into the dirname of the filename. So if the filename is debian/tmp/usr/bin, then that directory will be copied to debian/package/usr/. If the filename is debian/tmp/etc/passwd, it will be copied to debian/package/etc/. file|dir ... destdir Lists files (or directories) to install and where to install them to. The files will be installed into the first package dh_install acts on. LIMITATIONS
dh_install cannot rename files or directories, it can only install them with the names they already have into wherever you want in the package build tree. However, renaming can be achieved by using dh-exec with compatibility level 9 or later. An example debian/package.install file using dh- exec could look like: #!/usr/bin/dh-exec debian/default.conf => /etc/my-package/start.conf Please remember the following three things: o The package must be using compatibility level 9 or later (see debhelper(7)) o The package will need a build-dependency on dh-exec. o The install file must be marked as executable. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 11.1.6ubuntu2 2018-05-10 DH_INSTALL(1)