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

Resume aborted scp file transfers

Terminal - Resume aborted scp file transfers
rsync --partial --progress --rsh=ssh SOURCE DESTINATION
2009-02-16 16:22:10
User: episodeiv
Functions: rsync
14
Up
Down
Resume aborted scp file transfers

Put it into your sh startup script (I use

alias scpresume='rsync --partial --progress --rsh=ssh'

in bash). When a file transfer via scp has aborted, just use scpresume instead of scp and rsync will copy only the parts of the file that haven't yet been transmitted.

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 4 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

good tip, but

rsync -P SOURCE DESTINATION

is shorter (modern rsyncs default to ssh)

Comment by ger 165 weeks and 1 day ago

What about resuming a recursive transfer of thousands of files when after the first thousand, it was interrupted?

Comment by vgm64 159 weeks and 1 day ago

i think the best option would be

rsync -aP SOURCE DESTINATION

to preserve timestamp, user and group, continue, if copy is aborted and go recursively into directories:

-a, --archive archive mode; equals -rlptgoD (no -H,-A,-X)

-r, --recursive recurse into directories

-d, --dirs transfer directories without recursing

-l, --links copy symlinks as symlinks

-p, --perms preserve permissions

-o, --owner preserve owner (super-user only)

-g, --group preserve group

--devices preserve device files (super-user only)

--specials preserve special files

-D same as --devices --specials

-t, --times preserve modification times

--partial keep partially transferred files

--progress show progress during transfer

-P same as --partial --progress

@ vgm64: i thought, thats the "--partial" for

Comment by rubo77 139 weeks ago

Your point of view

You must be signed in to comment.

Related sites and podcasts