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.

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

Hide

Credits

Copy files over network using compression

Terminal - Copy files over network using compression
on the listening side: sudo nc -lp 2022 | sudo tar -xvf - and on the sending side: tar -cvzf - ./*| nc -w 3 name_of_listening_host 2022
2009-03-27 09:59:33
User: smcpherson
Functions: sudo tar
-2
Copy files over network using compression

This is useful for sending data between 2 computers that you have shell access to. Uses tar compression during transfer. Files are compressed & uncompressed automatically. Note the trailing dash on the listening side that makes netcat listen to stdin for data.

on the listening side:

sudo nc -lp 2022 | sudo tar -xvf -

explanation: open netcat to -l listen on -p port 2022, take the data stream and pipe to tar -x extract, -v verbose, -f using file filename - means "stdin"

on the sending side:

tar -cvzf - ./*| nc -w 3 name_of_listening_host 2022

explanation: compress all files in current dir using tar -c create, -v verbose, -f using file, - filename - here means "stdout" because we're tar -c instead of tar -x, -w3 wait 3 seconds on stream termination and then end the connection to the listening host name_of_listening_host, on port 2022

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

If you have scp on the client and the corresponding daemon on the server side, you can just use

scp filename user@host:/target/directory
Comment by DNSpyder 335 weeks and 2 days ago

Curious why a sudo is needed in "sudo nc -lp 2022"

(port 2022 is not a privileged port)?

Comment by mpb 335 weeks and 2 days ago

But where is the compression?

You should pipe your data through bzip2, gzip whatever.

Comment by OJM 335 weeks and 2 days ago

@OJM

Good catch - I left out the "-z" option that filters the archive through gzip. Post modified.

@mpb

I should have pointed out that port 2022 is arbitrary and was open for me when I needed this command. It could be replaced with whatever works for you though.

@DNSpyder

scp works, but the combination of netcat & tar is faster even with compression turned on in scp (-C).

Comment by smcpherson 335 weeks and 2 days ago

If you need encryption then use cryptcat:

http://sourceforge.net/projects/cryptcat/

Comment by OJM 335 weeks and 2 days ago

rsync

Comment by asmoore82 334 weeks and 5 days ago

This works in reverse, too, i.e. the listening side can be the "sender":

# on the listening/sending side tar -cvzf - ./* | nc -v -l 2022 # on the receiving side nc -v -w3 name_of_listening_host 2022 | tar -xvf -

The listening netcat will wait for the incoming connection before it starts sending the input piped from tar.

Comment by jordan 137 weeks and 2 days ago

Your point of view

You must be signed in to comment.