SFTP of SSH on linux doesn't support transfer resume?

Hi all,

It seemed that sftp of ssh on linux doesn't support transfer resume, is
there any ways to support it on linux/unix platform and can be used by
scripts?

Thanks

On Sat, 12 Jul 2008 09:10:48 +0800, newbie wrote:

> can be used by
> scripts?

If you're moving files from scripts, perhaps rsync [over ssh] is a
solution you should consider? It can resume, and do a lot more besides.

- Andrew

On Jul 12, 6:28 pm, Andrew Gideon <c172driv...@gideon.org> wrote:
> On Sat, 12 Jul 2008 09:10:48 +0800, newbie wrote:
> > can be used by
> > scripts?
>
> If you're moving files from scripts, perhaps rsync [over ssh] is a
> solution you should consider? It can resume, and do a lot more besides.
>
> - Andrew

The following blog seems to be explaining how to resume broken
downloads using rsync.
Haven't tried myself. You can give it a try.

http://joen.dk/wordpress/?p=34

But th downside is that the server should have rsync enabled.

- Neo
Techpulp Technologies
http://www.techpulp.com/

Hi Andrew/Neo,

I'll try it, thanks a lot.


"Neo - Techpulp" <(E-Mail Removed)>
??????:e636c27c-29d4-4470-818a-(E-Mail Removed)...
> On Jul 12, 6:28 pm, Andrew Gideon <c172driv...@gideon.org> wrote:
>> On Sat, 12 Jul 2008 09:10:48 +0800, newbie wrote:
>> > can be used by
>> > scripts?
>>
>> If you're moving files from scripts, perhaps rsync [over ssh] is a
>> solution you should consider? It can resume, and do a lot more besides.
>>
>> - Andrew
>
> The following blog seems to be explaining how to resume broken
> downloads using rsync.
> Haven't tried myself. You can give it a try.
>
> http://joen.dk/wordpress/?p=34
>
> But th downside is that the server should have rsync enabled.
>
> - Neo
> Techpulp Technologies
> http://www.techpulp.com/

On Sat, 12 Jul 2008 12:10:37 -0700, Neo - Techpulp wrote:

>
> The following blog seems to be explaining how to resume broken downloads
> using rsync.
> Haven't tried myself. You can give it a try.

That makes it sound like effort. Just add the --partial option, and
it'll happen.

In fact, though, the --partial option is required only to resume the file
that was being transferred at the moment of failure. Even w/o that
option set, if your transfer fails between files #4 and #5, files #1-#4
will not be sent again (unless they've been modified since their
transfer).

I use --partial all the time, BTW. No problems. It Just Works.

[...]

> But th downside is that the server should have rsync enabled.

Installed, but not "enabled", assuming that "enabled" means an rsync
daemon listening for rsync connections. I'm not recommending speaking to
an rsync daemon. Aside from anything else, this isn't secure. But rsync
can use alternate transports, and the default for this nowadays is ssh
(it used to be rsh; that 2006 blog article has out-of-date information).

If you:

rsync ... source-file-list destination-host:destination-path

then what actually occurs is:

* Local rsync opens SSH connection to destination-host as
if someone typed "ssh destination-host rsync"
* This starts rsync running at the destination-host end, with the
local and remote rsync processes speaking through the SSH
connection
* rsync stuff happens

Note that if you want to add ssh options (ie. specifying a key with -i),
this can be done with the --rsh="ssh -i ..." option to rsync.

- Andrew