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.


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.

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

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

Tags

Hide

Functions

Create a local compressed tarball from remote host directory

Terminal - Create a local compressed tarball from remote host directory
ssh user@host "tar -cf - /path/to/dir" | gzip > dir.tar.gz
2011-12-14 15:54:57
User: atoponce
Functions: gzip ssh
6
Create a local compressed tarball from remote host directory

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.

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
ssh user@host "tar -zcf - /path/to/dir" > dir.tar.gz
2011-12-16 05:48:38
User: __
Functions: ssh
Tags: ssh tar gzip
16

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.

ssh user@host "tar -czf - /path/to/dir" > dir.tar.gz

Know a better way?

If you can do better, submit your command here.

What others think

Useful +1

Comment by zlemini 157 weeks and 2 days ago

I needed to add some redirection after the pipe:

| gzip > dir.tar.gz
Comment by zlemini 157 weeks and 2 days ago

@zlemini Ah, yes. Simple typo, and fixed. Thanks!

Comment by atoponce 157 weeks and 2 days ago

Better to do the compression on the remote side; use 'tar czf' over there and just write it straight to a file here.

Comment by Mozai 157 weeks and 1 day ago

@Mozai I wouldn't necessarily say that doing compression remotely is "better", but it's certainly an alternate way of doing the command. If you're concerned about data bandwidth on the wire, OpenSSH (and many other SSH implementations) support compression to varying degrees. Lastly, not all tar(1) implementations support compression builtin. Best to keep the command 100% portable, as much as possible, than relying on platform-specific enhancements.

Comment by atoponce 157 weeks ago

There may be times where you have plenty of bandwidth but very short of remote processor so this could be useful in that case. I'd say it's usually better to do the compression on the remote side, though. You certainly wouldn't want to use ssh compression, because then you'd be compressing, decompressing, and compressing again. If your tar doesn't have the z option, you would use this:

ssh user@host "tar -cf - /path/to/dir | gzip" > dir.tar.gz

Also, if you didn't want "/path/to/dir" in each archive filename, you could do:

ssh user@host "cd /path/to/dir; tar -cf - . | gzip" > dir.tar.gz
Comment by splante 154 weeks and 3 days ago

you can use rsh with tar and gzip ,,,this url will guide you with examples.....

http://unixcommandstutorial.blogspot.in/2012/01/gzip-and-tar.html

Comment by parashuramsingh 149 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts