<?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"
	>
<channel>
	<title>Comments on: rm on steroids</title>
	<atom:link href="http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/</link>
	<description>Weblog Tools Blogging Tools Blog</description>
	<pubDate>Sat, 22 Nov 2008 09:41:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: jez</title>
		<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/#comment-501215</link>
		<dc:creator>jez</dc:creator>
		<pubDate>Sun, 02 Jul 2006 16:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/06/23/rm-on-steroids-in-linux/#comment-501215</guid>
		<description>&lt;blockquote cite="find . -name â€˜*.*â€™ -exec rm -rf {} \;"&gt;find . -name â€˜*.*â€™ -exec rm -rf {} \;&lt;/blockquote&gt; is really, &lt;em&gt;really&lt;/em&gt; mean :x</description>
		<content:encoded><![CDATA[<blockquote cite="find . -name â€˜*.*â€™ -exec rm -rf {} \;"><p>find . -name â€˜*.*â€™ -exec rm -rf {} \;</p></blockquote>
<p> is really, <em>really</em> mean <img src='http://weblogtoolscollection.com/wp-includes/images/smilies/icon_mad.gif' alt=':x' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Bailey</title>
		<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/#comment-488462</link>
		<dc:creator>Mike Bailey</dc:creator>
		<pubDate>Wed, 28 Jun 2006 20:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/06/23/rm-on-steroids-in-linux/#comment-488462</guid>
		<description>If you're converting from mod_php to phpsuexec on a cpanel system, the following commands help:

find /home/user/public_html/ -user nobody -exec chown user:user {} \;
find /home/user/public_html/ -perm 777 -exec chmod 755 {} \;

Run that for each user on the system, and you won't have any phpsuexec internal server errors.</description>
		<content:encoded><![CDATA[<p>If you&#8217;re converting from mod_php to phpsuexec on a cpanel system, the following commands help:</p>
<p>find /home/user/public_html/ -user nobody -exec chown user:user {} \;<br />
find /home/user/public_html/ -perm 777 -exec chmod 755 {} \;</p>
<p>Run that for each user on the system, and you won&#8217;t have any phpsuexec internal server errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zeroHalo</title>
		<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/#comment-488304</link>
		<dc:creator>zeroHalo</dc:creator>
		<pubDate>Wed, 28 Jun 2006 19:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/06/23/rm-on-steroids-in-linux/#comment-488304</guid>
		<description>Try

find . -name '*.*' -exec rm -rf {} \;

if you want to erase everything. Of course, I have yet to find a purpose for doing such except to be mean to *n*x newbies.

&lt;b&gt;NOTE:&lt;/b&gt; This will erase everything - do NOT try.</description>
		<content:encoded><![CDATA[<p>Try</p>
<p>find . -name &#8216;*.*&#8217; -exec rm -rf {} \;</p>
<p>if you want to erase everything. Of course, I have yet to find a purpose for doing such except to be mean to *n*x newbies.</p>
<p><b>NOTE:</b> This will erase everything - do NOT try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog of Leonid Mamchenkov</title>
		<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/#comment-488088</link>
		<dc:creator>Blog of Leonid Mamchenkov</dc:creator>
		<pubDate>Wed, 28 Jun 2006 18:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/06/23/rm-on-steroids-in-linux/#comment-488088</guid>
		<description>&lt;strong&gt;rm on steroids (a safer way)&lt;/strong&gt;

I came across an excellent tip about mixing rm and find commands in Linux shell.  
The only thing I&#8217;d add to it is a bit of safety.  Before executing the mix of find and rm, run the find command with the same options, but without rm.  It will pri...</description>
		<content:encoded><![CDATA[<p><strong>rm on steroids (a safer way)</strong></p>
<p>I came across an excellent tip about mixing rm and find commands in Linux shell.<br />
The only thing I&#8217;d add to it is a bit of safety.  Before executing the mix of find and rm, run the find command with the same options, but without rm.  It will pri&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/#comment-487764</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Wed, 28 Jun 2006 16:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/06/23/rm-on-steroids-in-linux/#comment-487764</guid>
		<description>I posted about this a few days ago:
http://raybdbomb.com/p/argument-list-too-long.html
&lt;blockquote&gt;find . -name '*\.*' &#124; xargs rm&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>I posted about this a few days ago:<br />
<a href="http://raybdbomb.com/p/argument-list-too-long.html">http://raybdbomb.com/p/argument-list-too-long.html</a></p>
<blockquote><p>find . -name &#8216;*\.*&#8217; | xargs rm</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/#comment-487679</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 28 Jun 2006 16:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/06/23/rm-on-steroids-in-linux/#comment-487679</guid>
		<description>Very good advice indeed. My post was much more general but the link explains things further.
The best advice is to use the find without the rm to see what gets included before using the rm in the exec.</description>
		<content:encoded><![CDATA[<p>Very good advice indeed. My post was much more general but the link explains things further.<br />
The best advice is to use the find without the rm to see what gets included before using the rm in the exec.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton Olsen</title>
		<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/#comment-487635</link>
		<dc:creator>Anton Olsen</dc:creator>
		<pubDate>Wed, 28 Jun 2006 16:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/06/23/rm-on-steroids-in-linux/#comment-487635</guid>
		<description>&lt;b&gt;Be very careful using &lt;i&gt;find&lt;/i&gt; to remove files.&lt;/b&gt;

The find command by default is recursive so any and all files in all subdirs below the current directory will go away too.

Using '*.*' for the pattern will miss all files without dots in them.  rm is not able to remove the directories so you will get an error for each of them found (include '.', the current dir).

If you really want to remove all files from the current directory through all it's subdirectories and leave the dirs alone then the better find parameters would be:
find . -type f -exec rm {} \;

You could also use "find . -exec rm {} \;" and ignore the errors rm throws out for the dirs.</description>
		<content:encoded><![CDATA[<p><b>Be very careful using <i>find</i> to remove files.</b></p>
<p>The find command by default is recursive so any and all files in all subdirs below the current directory will go away too.</p>
<p>Using &#8216;*.*&#8217; for the pattern will miss all files without dots in them.  rm is not able to remove the directories so you will get an error for each of them found (include &#8216;.&#8217;, the current dir).</p>
<p>If you really want to remove all files from the current directory through all it&#8217;s subdirectories and leave the dirs alone then the better find parameters would be:<br />
find . -type f -exec rm {} \;</p>
<p>You could also use &#8220;find . -exec rm {} \;&#8221; and ignore the errors rm throws out for the dirs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pablo Lopez Cienfuegos</title>
		<link>http://weblogtoolscollection.com/archives/2006/06/28/rm-on-steroids-in-linux/#comment-487586</link>
		<dc:creator>Pablo Lopez Cienfuegos</dc:creator>
		<pubDate>Wed, 28 Jun 2006 15:42:42 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/06/23/rm-on-steroids-in-linux/#comment-487586</guid>
		<description>Ok, that erases all your files with a dot in the name... What about "rm -rf ."?
</description>
		<content:encoded><![CDATA[<p>Ok, that erases all your files with a dot in the name&#8230; What about &#8220;rm -rf .&#8221;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
