Delete all files in folder without affecting load

find . -type f -exec echo echo rm {} '|' batch ';'|bash
While `echo rm * | batch` might seem to work, it might still raise the load of the system since `rm` will be _started_ when the load is low, but run for a long time. My proposed command executes a new `rm` execution once every minute when the load is small. Obviously, load could also be lower using `ionice`, but I still think this is a useful example for sequential batch jobs.
Sample Output
warning: commands will be executed using /bin/sh
job 40 at Fri Mar  1 16:07:00 2013
warning: commands will be executed using /bin/sh
job 41 at Fri Mar  1 16:07:00 2013
warning: commands will be executed using /bin/sh
job 42 at Fri Mar  1 16:07:00 2013
warning: commands will be executed using /bin/sh
job 43 at Fri Mar  1 16:07:00 2013

0
By: Ztyx
2013-03-01 15:14:08

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: