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

copy from host1 to host2, through your host

Terminal - copy from host1 to host2, through your host
ssh [email protected] "cd /somedir/tocopy/ && tar -cf - ." | ssh [email protected] "cd /samedir/tocopyto/ && tar -xf -"
2010-04-16 06:48:47
User: peshay
Functions: ssh
16
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.

Alternatives

There is 1 alternative - 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

This is a 'nocd' alternative :)

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 346 weeks and 2 days ago

for a certain file you could do

ssh [email protected] "tar -cf - certainfile" | ssh [email protected] "tar -xf -"

for text file you also may use something like

ssh [email protected] "cat certainfile.txt" | ssh [email protected] "cat >> certainfile.txt"

but I didn't tried it yet

Comment by peshay 346 weeks and 1 day ago

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

ssh [email protected] cat filename | ssh [email protected] 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 [email protected]:filename [email protected]:
Comment by tremby 346 weeks and 1 day 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 [email protected] cat filename | ssh [email protected] "cat >filename"

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

Comment by tremby 346 weeks and 1 day ago

Your point of view

You must be signed in to comment.