Hide

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.

Universal configuration monitoring and system of record for IT.
Hide

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:

Hide

News

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!
Hide

Top Tags

Hide

Functions

Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Create a local compressed tarball from remote host directory

Terminal - Create a local compressed tarball from remote host directory
ssh [email protected] "tar -zcf - /path/to/dir" > dir.tar.gz
2011-12-16 05:48:38
User: __
Functions: ssh
20
Create a local compressed tarball from remote host directory

This improves on #9892 by compressing the directory on the remote machine so that the amount of data transferred over the network is much smaller. The command uses ssh(1) to get to a remote host, uses tar(1) to archive and compress a remote directory, prints the result to STDOUT, which is written to a local file. In other words, we are archiving and compressing a remote directory to our local box.

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
ssh [email protected] "tar -cf - /path/to/dir" | gzip > dir.tar.gz
2011-12-14 15:54:57
User: atoponce
Functions: gzip ssh
Tags: ssh tar gzip
7

The command uses ssh(1) to get to a remote host, uses tar(1) to archive a remote directory, prints the result to STDOUT, which is piped to gzip(1) to compress to a local file. In other words, we are archiving and compressing a remote directory to our local box.

ssh [email protected] "tar -czf - /path/to/dir" > dir.tar.gz

Know a better way?

If you can do better, submit your command here.

What others think

Both solutions get the same result, but the firstone tries to minimize the bandwith usage, which should be an advantage at a slow network connection. The price fro that ist to squeeze out the cpu performance in two ways: ssh encryption and compressing.

The second solution needs more bandwith but use less cpu power, because the local host will compress the tarfile.

As often this is a tradeof between networkbandwith and cpu power. It depends also on the content of the tarfile, if it's compressable or not.

So there is no "better" alternative in any situation at least for me.

Comment by f4m8 260 weeks and 1 day ago

Definitely another way to get at the same result. However, OpenSSH (and other SSH implementations) support compression in the SSH connection. So, you can get the benefit of not burning the remote CPU (although you're using compression for the connection, you're not for both the connection and the archive simultaneously), and still minimize data transferred on the wire. Either way works.

Comment by atoponce 260 weeks ago

Your point of view

You must be signed in to comment.