<?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: More Linux and UNIX find command options</title>
	<atom:link href="http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/</link>
	<description>because I don't believe in life before coffee...</description>
	<lastBuildDate>Wed, 23 Nov 2011 03:01:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: tim</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-378927</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Mon, 06 Jun 2011 19:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-378927</guid>
		<description>this works great for avoiding paths to be printed where the said object is not present

find / name &quot;text&quot; 2&gt;/dev/null &#124; grep -r text

You can skip 2&gt;/dev/null altogether if you don&#039;t want to look at paths.</description>
		<content:encoded><![CDATA[<p>this works great for avoiding paths to be printed where the said object is not present</p>
<p>find / name &#8220;text&#8221; 2&gt;/dev/null | grep -r text</p>
<p>You can skip 2&gt;/dev/null altogether if you don&#8217;t want to look at paths.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J_R</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-375986</link>
		<dc:creator>J_R</dc:creator>
		<pubDate>Wed, 04 Aug 2010 11:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-375986</guid>
		<description>Using &quot;2&gt;/dev/null&quot; to prevent &quot;Permission denied&quot; does not work if trying to find which file(s) a particular piece of text occurs in e.g.

find . -type f -print &#124; xargs grep &quot;dctm.gif&quot; 2&gt;/dev/null

Only works with if you are trying to find an actual file(s)</description>
		<content:encoded><![CDATA[<p>Using &#8220;2&gt;/dev/null&#8221; to prevent &#8220;Permission denied&#8221; does not work if trying to find which file(s) a particular piece of text occurs in e.g.</p>
<p>find . -type f -print | xargs grep &#8220;dctm.gif&#8221; 2&gt;/dev/null</p>
<p>Only works with if you are trying to find an actual file(s)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-375581</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Fri, 19 Mar 2010 10:25:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-375581</guid>
		<description>Great tips and very useful.

Many thanks 
Jim</description>
		<content:encoded><![CDATA[<p>Great tips and very useful.</p>
<p>Many thanks<br />
Jim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shan</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-368748</link>
		<dc:creator>Shan</dc:creator>
		<pubDate>Tue, 13 May 2008 16:24:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-368748</guid>
		<description>Dealing with “Permission denied” in find  which is really useful to me. Especially When I try to find the largest files in solaris, I get this error. Now I am getting my desired output with out this error. Thanks for your tips.

With best regards
Shan</description>
		<content:encoded><![CDATA[<p>Dealing with “Permission denied” in find  which is really useful to me. Especially When I try to find the largest files in solaris, I get this error. Now I am getting my desired output with out this error. Thanks for your tips.</p>
<p>With best regards<br />
Shan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Emmons</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-346775</link>
		<dc:creator>Jon Emmons</dc:creator>
		<pubDate>Wed, 19 Dec 2007 01:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-346775</guid>
		<description>Gain,

From my experience &lt;code&gt;-mtime 3&lt;/code&gt; would return (and in this example remove) the files which were modified exactly 3 days ago.  &lt;code&gt;mtime -3&lt;/code&gt; finds files modified less than 3 days ago and &lt;code&gt;-mtime +3&lt;/code&gt; would find files modified more than three days ago.

I&#039;ve used this syntax on Linux and several varieties of UNIX but these things do vary by platform.  What platform have you used this on?  If there is a platform which has the results you mention I&#039;d like to add a warning to this article!

Thanks.</description>
		<content:encoded><![CDATA[<p>Gain,</p>
<p>From my experience <code>-mtime 3</code> would return (and in this example remove) the files which were modified exactly 3 days ago.  <code>mtime -3</code> finds files modified less than 3 days ago and <code>-mtime +3</code> would find files modified more than three days ago.</p>
<p>I&#8217;ve used this syntax on Linux and several varieties of UNIX but these things do vary by platform.  What platform have you used this on?  If there is a platform which has the results you mention I&#8217;d like to add a warning to this article!</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gian</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-346464</link>
		<dc:creator>gian</dc:creator>
		<pubDate>Tue, 18 Dec 2007 08:56:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-346464</guid>
		<description>hello Jon,
thanks for the help.
just to make you notice that:
$ find . -name &#039;*.txt&#039; -mtime -3 -exec rm {} \;
will delete all txt files, since &quot;-3&quot; means &quot;with a date that is 3 days ahead&quot;. If you wish to delete files which are 3 days older you should type:
$ find . -name &#039;*.txt&#039; -mtime 3 -exec rm {} \;
ciao</description>
		<content:encoded><![CDATA[<p>hello Jon,<br />
thanks for the help.<br />
just to make you notice that:<br />
$ find . -name &#8216;*.txt&#8217; -mtime -3 -exec rm {} \;<br />
will delete all txt files, since &#8220;-3&#8243; means &#8220;with a date that is 3 days ahead&#8221;. If you wish to delete files which are 3 days older you should type:<br />
$ find . -name &#8216;*.txt&#8217; -mtime 3 -exec rm {} \;<br />
ciao</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-325538</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Wed, 14 Nov 2007 14:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-325538</guid>
		<description>Thanks! Useful!</description>
		<content:encoded><![CDATA[<p>Thanks! Useful!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-163286</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 04 May 2007 15:27:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-163286</guid>
		<description>&quot;Dealing with “Permission denied” in find&quot;

-- thanks Jon, that was exactly the command I was just looking for :)</description>
		<content:encoded><![CDATA[<p>&#8220;Dealing with “Permission denied” in find&#8221;</p>
<p>&#8211; thanks Jon, that was exactly the command I was just looking for <img src='http://www.lifeaftercoffee.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/comment-page-1/#comment-163280</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Fri, 04 May 2007 14:41:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.lifeaftercoffee.com/2007/05/02/more-linux-and-unix-find-command-options/#comment-163280</guid>
		<description>An easy way to get rid of the error messages is to have find test for permissions before trying to go into the directory:

For example to look for files named &quot;help&quot; use find like this:

&lt;code&gt;find . \( -type d ! -exec test -x {} -a -r {} \; -prune \) -o \( -name help ) -exec ls -ld {} \;&lt;/code&gt;

The crucial part is &lt;code&gt;-type d ! -exec test -x {} -a -r {} \; -prune&lt;/code&gt; which test for the readability of the directory and does not traverse it if it is not readable or executable.</description>
		<content:encoded><![CDATA[<p>An easy way to get rid of the error messages is to have find test for permissions before trying to go into the directory:</p>
<p>For example to look for files named &#8220;help&#8221; use find like this:</p>
<p><code>find . \( -type d ! -exec test -x {} -a -r {} \; -prune \) -o \( -name help ) -exec ls -ld {} \;</code></p>
<p>The crucial part is <code>-type d ! -exec test -x {} -a -r {} \; -prune</code> which test for the readability of the directory and does not traverse it if it is not readable or executable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

