What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags





Truncate logs in unix

Terminal - Truncate logs in unix
logs=$(find . -name *.log);for log in $logs; do cat /dev/null > $log;done
2009-03-04 10:05:48
Functions: cat find
Truncate logs in unix

This find files of name like *.log and truncates them.


There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

logs=$(find . -name *.log);

for log in $logs;

do echo "" > $log;


Comment by H4rpy 322 weeks ago

find . -type f -name "log*" -print0 | xargs -0 truncate -s 0

Comment by OJM 322 weeks ago

If "truncate" is not available this should do the trick:

find . -type f -name "log*" -print0 | xargs -0 -i /bin/sh -c 'echo -n "" > {}'

Comment by OJM 322 weeks ago

find . -type f -iname '*log'|while read logfile; do >$logfile; done

Comment by linuxrawkstar 322 weeks ago

@linuxrawkstar: Broken if filename contains whitespaces.

Comment by OJM 322 weeks ago

if your log filename contains whitepsace *you* are broken

Comment by maht 321 weeks and 6 days ago

You guys are forgetting the -exec flag on find. Try this:

find . -type f -name '*.log' -exec tee {} </dev/null \;

Or, if you have truncate (I don't, and it doesn't seem to be in the Ubuntu repos):

find . -type f -name '*.log' -exec truncate -s 0 {} \;
Comment by goodevilgenius 321 weeks and 3 days ago

find . -type f -name '*.log' -exec cp /dev/null '{}' \;

Handles spaces in file names (never assume filenames won't have spaces in them).

Comment by Mehuge 302 weeks and 4 days ago

Your point of view

You must be signed in to comment.