Find - Revision history

Jimbo: Reverted edits by 58.185.16.210 (Talk); changed back to last version by Jimbo

2007-11-19T17:45:36Z

Reverted edits by 58.185.16.210 (Talk); changed back to last version by Jimbo

190.129.118.1 at 18:31, 18 September 2007

2007-09-18T18:31:46Z

68.118.4.45 at 19:35, 18 June 2007

2007-06-18T19:35:39Z

Jimbo: /* Refine results by piping through grep */

2006-05-28T05:20:25Z

Refine results by piping through grep

Jimbo at 05:19, 28 May 2006

2006-05-28T05:19:44Z

Dave at 17:34, 22 February 2005

2005-02-22T17:34:42Z

Jimbo at 00:08, 26 August 2004

2004-08-26T00:08:50Z

Jimbo at 20:20, 25 August 2004

2004-08-25T20:20:29Z

Dave at 19:57, 25 August 2004

2004-08-25T19:57:32Z

Dave at 19:57, 25 August 2004

2004-08-25T19:57:13Z

@@ Line 22: / Line 22: @@
 Let's say you want to delete all files and directories created more than 30 days ago in the current directory (notice that maxdepth is '''one''', not zero as you might think):
-  server# '''find . -ctime  30 -maxdepth 1 -delete'''
+  server# '''find . -ctime +30 -maxdepth 1 -delete'''
 What if you only want to delete all ''files'', but not directories, in the current directory ''and'' all of its subdirectories?
-  server# '''find . -ctime  30 -type f -delete'''
+  server# '''find . -ctime +30 -type f -delete'''
 What if we want to delete everything in the current directory that hasn't been accessed this year?
-  server# '''find . -atime  365 -maxdepth 1 -delete'''
+  server# '''find . -atime +365 -maxdepth 1 -delete'''
 == Doing things to the files you find ==

@@ Line 22: / Line 22: @@
 Let's say you want to delete all files and directories created more than 30 days ago in the current directory (notice that maxdepth is '''one''', not zero as you might think):
-  server# '''find . -ctime +30 -maxdepth 1 -delete'''
+  server# '''find . -ctime  30 -maxdepth 1 -delete'''
 What if you only want to delete all ''files'', but not directories, in the current directory ''and'' all of its subdirectories?
-  server# '''find . -ctime +30 -type f -delete'''
+  server# '''find . -ctime  30 -type f -delete'''
 What if we want to delete everything in the current directory that hasn't been accessed this year?
-  server# '''find . -atime +365 -maxdepth 1 -delete'''
+  server# '''find . -atime  365 -maxdepth 1 -delete'''
 == Doing things to the files you find ==

@@ Line 10: / Line 10: @@
 With the above, you won't waste time and valuable system resources thrashing all hard drives looking for a file you know can't be anywhere other than /usr/home.
-== Refine results by [[piping]] through [[grep]] ==
+== Refine results by [[pipe|piping]] through [[grep]] ==
 If you're receiving too many results and you want to narrow them down somewhat, you can pipe the results through [[grep]] for easier review - let's say you're looking for a file that contains "string", and you also know it contains "silly", but you don't know whether it's "sillystring" or "string,silly" or "silly_string" or... you get the idea.  Try this:

@@ Line 1: / Line 1: @@
 Used to [[find]] files or directories. For bare-bones help in finding a particular file or directory, use in conjunction with the '''-name''' argument:
@@ Line 7: / Line 8: @@
   '''samizdata#''' find /usr/home -name "string"
-With the above, you won't waste time and valuable system resources thrashing all hard drives looking for a file you know can't be anywhere other than /usr/home.  If you're receiving too many results and you want to narrow them down somewhat, you can pipe the results through [[grep]] for easier review - let's say you're looking for a file that contains "string", and you also know it contains "silly", but you don't know whether it's "sillystring" or "string,silly" or "silly_string" or... you get the idea.  Try this:
+With the above, you won't waste time and valuable system resources thrashing all hard drives looking for a file you know can't be anywhere other than /usr/home.
   '''samizdata#''' find /usr/home -name "string" | grep "silly"
@@ Line 14: / Line 18: @@
   '''samizdata#''' find /usr/home -name "string" | grep "silly" | more
 Even after all this, we've barely scratched the surface of what you can do with [[find]] - it's a complicated beast that is well worth the time spent in investigating further via the [[man]] pages.
-See also [[locate]] for a far more optimized method of searching for files by substring, using a database generated by the weekly [[periodic]] routines rather than a brute-force search of the filesystem itself.
+== See also: ==
 [[category: System Commands]]
 [[Category : New_User_Tips_and_FAQs]]

← Older revision		Revision as of 17:34, 22 February 2005
Line 20:		Line 20:

	[[category: System Commands]]		[[category: System Commands]]
		+	[[Category : New_User_Tips_and_FAQs]]

← Older revision		Revision as of 00:08, 26 August 2004
Line 19:		Line 19:
	See also [[locate]] for a far more optimized method of searching for files by substring, using a database generated by the weekly [[periodic]] routines rather than a brute-force search of the filesystem itself.		See also [[locate]] for a far more optimized method of searching for files by substring, using a database generated by the weekly [[periodic]] routines rather than a brute-force search of the filesystem itself.

−	[[category: ~~system commands~~]]	+	[[category: System Commands]]

@@ Line 1: / Line 1: @@
-Used to [[find]] files or directories. A complicated beast that is worth it's time in finding out more about via the [[man]] pages. For bare-bones help in finding a particular file or directory, use in conjunction with [[grep]]:
+Used to [[find]] files or directories. For bare-bones help in finding a particular file or directory, use in conjunction with the '''-name''' argument:
-  samizdata# find / | grep "string"
+  '''samizdata#''' find / -name "string"
-will execute [[find]] on [[ /]]  and then only show you the results that match "string". Note that this is ''not'' optimal and can take a while on large systems.
+will execute [[find]] on [[ /]]  and then only show you the results that match "string".  Note that this is ''not'' a fast search and can take a very long time and burn a lot of system resources when used on large (or multiple) filesystems - in this example, every single device and filesystem on the machine will be groveled over directly looking for anything with "string" in the filename.  If you knew that the file you wanted to find was in a user's home directory, for example, you would be much better off with the following:
 [[category: system commands]]

@@ Line 3: / Line 3: @@
   samizdata# find / | grep "string"
-will execute [[find]] on [[/]] and then only show you the results that match "string". Note that this is ''not'' optimal and can take a while on large systems.
+will execute [[find]] on [[ / ]] and then only show you the results that match "string". Note that this is ''not'' optimal and can take a while on large systems.
 [[category: system commands]]