<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Tip: Using find Command in Linux</title>
	<atom:link href="http://www.pinoytux.com/linux/tip-using-find-command-in-linux/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pinoytux.com/linux/tip-using-find-command-in-linux</link>
	<description>Everything Linux</description>
	<lastBuildDate>Sat, 11 Feb 2012 02:25:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dennis quek</title>
		<link>http://www.pinoytux.com/linux/tip-using-find-command-in-linux/comment-page-1#comment-50874</link>
		<dc:creator>Dennis quek</dc:creator>
		<pubDate>Tue, 02 Dec 2008 10:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pinoytux.com/?p=530#comment-50874</guid>
		<description>I kept having problems with the stupid error msg saying find: paths must precede expressions.</description>
		<content:encoded><![CDATA[<p>I kept having problems with the stupid error msg saying find: paths must precede expressions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maldito</title>
		<link>http://www.pinoytux.com/linux/tip-using-find-command-in-linux/comment-page-1#comment-50540</link>
		<dc:creator>maldito</dc:creator>
		<pubDate>Fri, 21 Nov 2008 07:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.pinoytux.com/?p=530#comment-50540</guid>
		<description>i prefer &quot;-iname&quot; over &quot;-name&quot; to make it case insensitive.</description>
		<content:encoded><![CDATA[<p>i prefer &#8220;-iname&#8221; over &#8220;-name&#8221; to make it case insensitive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amit Agarwal</title>
		<link>http://www.pinoytux.com/linux/tip-using-find-command-in-linux/comment-page-1#comment-50509</link>
		<dc:creator>Amit Agarwal</dc:creator>
		<pubDate>Thu, 20 Nov 2008 16:52:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.pinoytux.com/?p=530#comment-50509</guid>
		<description>find . -empty -delete 

I like this one and other thing I like is that mostly all -exec rm -rf {} \; can be replaced with -delete</description>
		<content:encoded><![CDATA[<p>find . -empty -delete </p>
<p>I like this one and other thing I like is that mostly all -exec rm -rf {} \; can be replaced with -delete</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Whittaker</title>
		<link>http://www.pinoytux.com/linux/tip-using-find-command-in-linux/comment-page-1#comment-50465</link>
		<dc:creator>Peter Whittaker</dc:creator>
		<pubDate>Wed, 19 Nov 2008 18:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.pinoytux.com/?p=530#comment-50465</guid>
		<description>For finding files older than a certain time, you might want to use relative time, e.g., 

   $ find /home -mtime +1

The commands provided only find files modified 24 hours ago; this example finds files modified 24 hours or more ago. Likewise,

    $ find /home -mtime 1

finds files modified about 24 hours ago, while

   $ find /home -mtime 0

and 

    $ find /home -mtime -1

both find files modified less than 24 hours ago, but don&#039;t find quite the same files, due to slight rounding differences when find calculates the time period.

One of the first changes I used to make any Unix system I inherited was to replace the &quot;rm -rf /tmp/*&quot; command found in startup scripts with

    find /tmp -mtime +7 -exec /bin/rm -rf {} \;

which deletes all files/directories unmmodified in more than 7 days. Why? Because sometimes /tmp contains core and log files useful to figuring out why your system crashed - and having &quot;rm -rf /tmp/*&quot; in startup scripts cleaned them out.</description>
		<content:encoded><![CDATA[<p>For finding files older than a certain time, you might want to use relative time, e.g., </p>
<p>   $ find /home -mtime +1</p>
<p>The commands provided only find files modified 24 hours ago; this example finds files modified 24 hours or more ago. Likewise,</p>
<p>    $ find /home -mtime 1</p>
<p>finds files modified about 24 hours ago, while</p>
<p>   $ find /home -mtime 0</p>
<p>and </p>
<p>    $ find /home -mtime -1</p>
<p>both find files modified less than 24 hours ago, but don&#8217;t find quite the same files, due to slight rounding differences when find calculates the time period.</p>
<p>One of the first changes I used to make any Unix system I inherited was to replace the &#8220;rm -rf /tmp/*&#8221; command found in startup scripts with</p>
<p>    find /tmp -mtime +7 -exec /bin/rm -rf {} \;</p>
<p>which deletes all files/directories unmmodified in more than 7 days. Why? Because sometimes /tmp contains core and log files useful to figuring out why your system crashed &#8211; and having &#8220;rm -rf /tmp/*&#8221; in startup scripts cleaned them out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jklowden</title>
		<link>http://www.pinoytux.com/linux/tip-using-find-command-in-linux/comment-page-1#comment-50462</link>
		<dc:creator>jklowden</dc:creator>
		<pubDate>Wed, 19 Nov 2008 16:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.pinoytux.com/?p=530#comment-50462</guid>
		<description>Quoting {} is unnecessary:

&lt;code&gt;
$ touch &quot;a b&quot;
$ find . -name a\*b
./a b
$ find . -name a\*b -exec ls {} \;
./a b
$ find . -name a\*b -exec rm {} \;
$ find . -name a\*b
$
&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Quoting {} is unnecessary:</p>
<p><code><br />
$ touch "a b"<br />
$ find . -name a\*b<br />
./a b<br />
$ find . -name a\*b -exec ls {} \;<br />
./a b<br />
$ find . -name a\*b -exec rm {} \;<br />
$ find . -name a\*b<br />
$<br />
</code></p>
]]></content:encoded>
	</item>
</channel>
</rss>

