<?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: /bin/rm annoying limitation: Argument list too long</title> <atom:link href="http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/feed/" rel="self" type="application/rss+xml" /><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/</link> <description>The Journal Of A Linux Sysadmin</description> <lastBuildDate>Sat, 31 Jul 2010 13:48:55 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0</generator> <item><title>By: werkun</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-2/#comment-181896</link> <dc:creator>werkun</dc:creator> <pubDate>Thu, 10 Jun 2010 22:55:45 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-181896</guid> <description>Very useful when you wanna remove 170000 files, thanks a lot!</description> <content:encoded><![CDATA[<p>Very useful when you wanna remove 170000 files, thanks a lot!</p> ]]></content:encoded> </item> <item><title>By: ???</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-2/#comment-180979</link> <dc:creator>???</dc:creator> <pubDate>Fri, 04 Sep 2009 13:49:49 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-180979</guid> <description>thanx for sharing to the netiziens</description> <content:encoded><![CDATA[<p>thanx for sharing to the netiziens</p> ]]></content:encoded> </item> <item><title>By: loooloow</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-2/#comment-179996</link> <dc:creator>loooloow</dc:creator> <pubDate>Thu, 02 Apr 2009 16:08:31 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-179996</guid> <description>thanks to much really nice .... but i need your help in this question
The goal of this assignment is to write a shell script to replace the rm command andprovide undelete capability similar to MS-DOS.Write a shell program to duplicate the UNIX rm command with the following features:1.It will have a switch -i that will act in the same manner as in the rm command.2.Instead of deleting the files, it will move them to a wastebasket directory. If thefile already exists in the wastebasket directory, then the existing file (in thewastebasket) will have the version number zero appended to it and the newlydeleted file will have version number one appended to it. If the version numbersetup is already in use for that file then the newest one will simply have the nextversion number in the series appended to it. It&#039;s your choice as to what system touse for this. Just be sure that it is a unique system and will not be part of anynormal file naming convention you might use.3.It will have a switch -c that will clear the entire wastebasket after asking forconfirmation. The -i and -c switches may be combined to ask for confirmation onindividual files.Don&#039;t forget that wildcards and multiple files are allowed on the command line. Theswitches when combined may be in any order but must be before any filenames. Yourprogram must also catch any operator errors.
i hope to answer me in my email
thanks ...</description> <content:encoded><![CDATA[<p>thanks to much really nice &#8230;. but i need your help in this question<br
/> The goal of this assignment is to write a shell script to replace the rm command andprovide undelete capability similar to MS-DOS.Write a shell program to duplicate the UNIX rm command with the following features:1.It will have a switch -i that will act in the same manner as in the rm command.2.Instead of deleting the files, it will move them to a wastebasket directory. If thefile already exists in the wastebasket directory, then the existing file (in thewastebasket) will have the version number zero appended to it and the newlydeleted file will have version number one appended to it. If the version numbersetup is already in use for that file then the newest one will simply have the nextversion number in the series appended to it. It&#8217;s your choice as to what system touse for this. Just be sure that it is a unique system and will not be part of anynormal file naming convention you might use.3.It will have a switch -c that will clear the entire wastebasket after asking forconfirmation. The -i and -c switches may be combined to ask for confirmation onindividual files.Don&#8217;t forget that wildcards and multiple files are allowed on the command line. Theswitches when combined may be in any order but must be before any filenames. Yourprogram must also catch any operator errors.<br
/> i hope to answer me in my email<br
/> thanks &#8230;</p> ]]></content:encoded> </item> <item><title>By: Eligio</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-2/#comment-179666</link> <dc:creator>Eligio</dc:creator> <pubDate>Sun, 08 Feb 2009 12:08:10 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-179666</guid> <description>command works on my 7k+ swf files, thanks for the solution. :D</description> <content:encoded><![CDATA[<p>command works on my 7k+ swf files, thanks for the solution. <img
src='http://www.ducea.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /></p> ]]></content:encoded> </item> <item><title>By: Burg</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-1/#comment-178737</link> <dc:creator>Burg</dc:creator> <pubDate>Fri, 24 Oct 2008 13:14:34 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-178737</guid> <description>cd /var/spool/mqueue/
find . -name &#039;dfm3*&#039; &#124; xargs rm</description> <content:encoded><![CDATA[<p>cd /var/spool/mqueue/<br
/> find . -name &#8216;dfm3*&#8217; | xargs rm</p> ]]></content:encoded> </item> <item><title>By: David Newcomb</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-1/#comment-178433</link> <dc:creator>David Newcomb</dc:creator> <pubDate>Sat, 09 Aug 2008 19:00:14 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-178433</guid> <description>Often the reason why there are loads of files in a folder is because it is a logs folder and you haven&#039;t been doing your house keeping properly. In these situations you rarely want to delete all of them. Usually you want to keep the last 30 days worth of files. So find is a far better solution, or bigdel documented here:http://www.bigsoft.co.uk/blog/index.php/2008/08/09/rm-argument-list-too-long</description> <content:encoded><![CDATA[<p>Often the reason why there are loads of files in a folder is because it is a logs folder and you haven&#8217;t been doing your house keeping properly. In these situations you rarely want to delete all of them. Usually you want to keep the last 30 days worth of files. So find is a far better solution, or bigdel documented here:</p><p><a
href="http://www.bigsoft.co.uk/blog/index.php/2008/08/09/rm-argument-list-too-long" rel="nofollow">http://www.bigsoft.co.uk/blog/index.php/2008/08/09/rm-argument-list-too-long</a></p> ]]></content:encoded> </item> <item><title>By: Shell parameter size limitation: Argument list too long &#124; Eric Cheng&#8217;s Journal</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-1/#comment-126084</link> <dc:creator>Shell parameter size limitation: Argument list too long &#124; Eric Cheng&#8217;s Journal</dc:creator> <pubDate>Tue, 29 Jan 2008 20:23:15 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-126084</guid> <description>[...] then, I found another hint (the comments are the useful part), and tried: ls post*.jpg &#124; xargs chmod [...]</description> <content:encoded><![CDATA[<p>[...] then, I found another hint (the comments are the useful part), and tried: ls post*.jpg | xargs chmod [...]</p> ]]></content:encoded> </item> <item><title>By: kep1269</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-1/#comment-108052</link> <dc:creator>kep1269</dc:creator> <pubDate>Thu, 29 Nov 2007 20:17:49 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-108052</guid> <description>Thanks Marius..I found that there is a limitation on mtime due to it having to sort...  My problem stems from there being roughly 250,000 files in the directory.I ended up just piping ls -rt to a file.sh and modding that to rm the files... took a long time, but worked.</description> <content:encoded><![CDATA[<p>Thanks Marius..</p><p>I found that there is a limitation on mtime due to it having to sort&#8230;  My problem stems from there being roughly 250,000 files in the directory.</p><p>I ended up just piping ls -rt to a file.sh and modding that to rm the files&#8230; took a long time, but worked.</p> ]]></content:encoded> </item> <item><title>By: - Marius -</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-1/#comment-108049</link> <dc:creator>- Marius -</dc:creator> <pubDate>Thu, 29 Nov 2007 19:49:14 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-108049</guid> <description>kp1269: that should work just by adding something like:
find . â€˜*.wrkâ€™ -mtime 30 -print0 &#124; xargs -0 rm -fIf for some reason that doesn&#039;t work for you, you might want to try -mmin +xx and translate in minutes the time you need. hth.</description> <content:encoded><![CDATA[<p>kp1269: that should work just by adding something like:<br
/> find . â€˜*.wrkâ€™ -mtime 30 -print0 | xargs -0 rm -f</p><p>If for some reason that doesn&#8217;t work for you, you might want to try -mmin +xx and translate in minutes the time you need. hth.</p> ]]></content:encoded> </item> <item><title>By: kp1269</title><link>http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/comment-page-1/#comment-107389</link> <dc:creator>kp1269</dc:creator> <pubDate>Tue, 27 Nov 2007 22:54:13 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/05/24/binrm-annoying-limitation-argument-list-too-long/#comment-107389</guid> <description>I have usedfind /some/directory -name â€˜*.wrkâ€™ -print0 &#124; xargs -n1000 -0 rm -f
and
find . â€˜*.wrkâ€™ -print0 &#124; xargs  -0 rm -fIs there any way to do this with -mtime to delet files older than sya 30 days? (i can&#039;t get it to work)</description> <content:encoded><![CDATA[<p>I have used</p><p>find /some/directory -name â€˜*.wrkâ€™ -print0 | xargs -n1000 -0 rm -f<br
/> and<br
/> find . â€˜*.wrkâ€™ -print0 | xargs  -0 rm -f</p><p>Is there any way to do this with -mtime to delet files older than sya 30 days? (i can&#8217;t get it to work)</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: www.ducea.com @ 2010-07-31 16:42:10 by W3 Total Cache -->