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.

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.

UpGuard checks and validates configurations for every major OS, network device, and cloud provider.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Archive every file in /var/logs

Terminal - Archive every file in /var/logs
find /var/logs -name * | xargs tar -jcpf logs_`date +%Y-%m-%e`.tar.bz2
2009-06-02 19:48:47
Functions: find tar xargs
Archive every file in /var/logs

Know a better way?

If you can do better, submit your command here.

What others think

This doesn't work because the shell expands the asterisk. You need to quote it. Another problem is that the tar file will contain the absolute path names of the log files, which is usually undesirable.

Also, for regular usage, it is not a good idea to archive "live" log files that are currently growing. It's better to rotate them and then archive the rotated files. In other words, the archiving of log files should be part of the script that performs the rotation (a nightly cron job or whatever).

On a side note, please use $() instead of backticks for command substitution. Technically both work the same, but backticks have a bunch of disadvantages: They can easily be confused with single quotes or apostrophes, and quoting becomes difficult and error-prone, especially if you need to nest multiple levels of command substitution.

Comment by inof 463 weeks and 6 days ago

And, most distros can rotate & compress logfiles automatically anyways using the logrotate package (at least in debian/ubuntu). Logrotate usually runs as a cron job every hour/day/week/month/etc. See 'man logrotate' and /etc/logrotate.conf for more...

Comment by bwoodacre 463 weeks and 5 days ago

Your point of view

You must be signed in to comment.