<?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: How to resolve the &#039;/bin/rm: Argument list too long&#039; error</title>
	<atom:link href="http://www.simplehelp.net/2009/02/18/linux-tip-overcoming-the-binrm-argument-list-too-long-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.simplehelp.net/2009/02/18/linux-tip-overcoming-the-binrm-argument-list-too-long-error/</link>
	<description>Common questions, simple answers</description>
	<lastBuildDate>Mon, 23 Nov 2009 06:40:21 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: myhnet</title>
		<link>http://www.simplehelp.net/2009/02/18/linux-tip-overcoming-the-binrm-argument-list-too-long-error/comment-page-1/#comment-10573</link>
		<dc:creator>myhnet</dc:creator>
		<pubDate>Wed, 25 Feb 2009 08:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplehelp.net/?p=2262#comment-10573</guid>
		<description>find . -type f  -exec rm {} \;</description>
		<content:encoded><![CDATA[<p>find . -type f  -exec rm {} \;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MikeT</title>
		<link>http://www.simplehelp.net/2009/02/18/linux-tip-overcoming-the-binrm-argument-list-too-long-error/comment-page-1/#comment-10575</link>
		<dc:creator>MikeT</dc:creator>
		<pubDate>Fri, 20 Feb 2009 02:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplehelp.net/?p=2262#comment-10575</guid>
		<description>Good catch using the print0 option, that&#039;s an important one.

Most find commands do not require the &quot;-name&quot; predicate. What&#039;s usually more important is to make sure you&#039;re deleting *files* and not something else you might not have intended. For this use &quot;-type f&quot; inplace of the &quot;-name&quot; option....

find  .  -type f -print0 &#124; xargs -0 /bin/rm

A) Use the full path to the &#039;rm&#039; command so your aliases don&#039;t muck with things.
B) Check your xargs command, you can sometimes, if needed, tell it to use one &quot;result&quot; at a time, such as (if you didn&#039;t use print0 but regular print) &quot;-l1&quot;</description>
		<content:encoded><![CDATA[<p>Good catch using the print0 option, that&#8217;s an important one.</p>
<p>Most find commands do not require the &#8220;-name&#8221; predicate. What&#8217;s usually more important is to make sure you&#8217;re deleting *files* and not something else you might not have intended. For this use &#8220;-type f&#8221; inplace of the &#8220;-name&#8221; option&#8230;.</p>
<p>find  .  -type f -print0 | xargs -0 /bin/rm</p>
<p>A) Use the full path to the &#8216;rm&#8217; command so your aliases don&#8217;t muck with things.<br />
B) Check your xargs command, you can sometimes, if needed, tell it to use one &#8220;result&#8221; at a time, such as (if you didn&#8217;t use print0 but regular print) &#8220;-l1&#8243;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aleš Friedl</title>
		<link>http://www.simplehelp.net/2009/02/18/linux-tip-overcoming-the-binrm-argument-list-too-long-error/comment-page-1/#comment-10574</link>
		<dc:creator>Aleš Friedl</dc:creator>
		<pubDate>Thu, 19 Feb 2009 15:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplehelp.net/?p=2262#comment-10574</guid>
		<description>Safe variant for filenames with spaces, new lines and other whitespace characters:
find . -name &#039;*&#039; -print0 &#124; xargs -o rm</description>
		<content:encoded><![CDATA[<p>Safe variant for filenames with spaces, new lines and other whitespace characters:<br />
find . -name &#8216;*&#8217; -print0 | xargs -o rm</p>
]]></content:encoded>
	</item>
</channel>
</rss>
