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.

OpenID
or
Sign in Register

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

Hide

Credits

Site by David Winterbottom (user root).

copy from host1 to host2, through your host

Terminal - copy from host1 to host2, through your host
ssh root@host1 "cd /somedir/tocopy/ && tar -cf - ." | ssh root@host2 "cd /samedir/tocopyto/ && tar -xf -"
2010-04-16 06:48:47
User: peshay
Functions: ssh
15
Up
Down
copy from host1 to host2, through your host

Good if only you have access to host1 and host2, but they have no access to your host (so ncat won't work) and they have no direct access to each other.

Add to favourites | Report as malicious

Alternatives

There are 6 alternatives - vote for the best!

Terminal - Alternatives
ssh user@<source_host> -- tar cz <path> | ssh user@<destination_host> -- tar vxzC <path>
2010-04-20 12:30:49
User: dranan
Functions: ssh tar
2
Up
Down
copy from host1 to host2, through your host

This is a 'nocd' alternative :)

Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

i like this, but it takes the content of the directory you copy from and puts it where you specify, i'm not quite sure how you would do a certain file without takign the whole directory.

Comment by alf 165 weeks and 4 days ago

for a certain file you could do

ssh root@host1 "tar -cf - certainfile" | ssh root@host2 "tar -xf -"

for text file you also may use something like

ssh root@host1 "cat certainfile.txt" | ssh root@host2 "cat >> certainfile.txt"

but I didn't tried it yet

Comment by peshay 165 weeks and 4 days ago

There's no reason to use tar at all if it's just a single file -- you could do

ssh root@host1 cat filename | ssh root@host2 cat >filename

This method means typing the filename twice, though.

But it's worth noting that if host1 can log in to host2 directly (and it seems you need to have SSH keys set up so host2 won't ask for a password from host1) you can do

scp root@host1:filename root@host2:
Comment by tremby 165 weeks and 4 days ago

That first example should have had host2's commands in quotes otherwise it'll redirect to a file on your local machine. So

ssh root@host1 cat filename | ssh root@host2 "cat >filename"

No quotes are needed for command for host1 in this case.

Comment by tremby 165 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts