Re: [Duplicity-talk] why is rsync backend using ssh?

[Tim Riemenschneider]

address@hidden schrieb:
> while checking out the rsync backend I got confused
>
> in plain command line the following happens:
>
> #> rsync /tmp rsync://address@hidden/test -vvv
> opening tcp connection to host port 873
> rsync: getaddrinfo: host 873: Name or service not known
>
> but the same call in duplicity's rsync backend connects to ssh (port
> 22). see below.
> I couldn't figure out how the backend switches modes. Interestingly
> defining an url like
> rsync://user:address@hidden::test
> seems not to utilize ssh.
>
> What am I missing? .. thanks ede/duply.net
I think that is exactly as intended:
"duplicity rsync://address@hidden/some_relative_dir" and "duplicity
rsync://address@hidden//some_absolute_dir" do rsync-over-ssh, that is the same 
as
"rsync address@hidden:some_relative_dir" and "rsync
address@hidden:/some_absolute_dir" (note the absence of rsync:// in the url)
rsync:// in the duplicity url defines the duplicity-backend, not the
protocol for rsync.

In contrast to this:
"duplicity rsync://address@hidden::module/dir" uses the rsync-daemon.
"rsync address@hidden::module/dir" does so, too. "rsync
rsync://address@hidden/module/dir" is an alias for this.

See also "man rsync":

    SYNOPSIS
           Local:  rsync [OPTION...] SRC... [DEST]

           Access via remote shell:
             Pull: rsync [OPTION...] address@hidden:SRC... [DEST]
             Push: rsync [OPTION...] SRC... address@hidden:DEST

           Access via rsync daemon:
             Pull: rsync [OPTION...] address@hidden::SRC... [DEST]
                   rsync [OPTION...] rsync://address@hidden:PORT]/SRC...
    [DEST]
             Push: rsync [OPTION...] SRC... address@hidden::DEST
                   rsync [OPTION...] SRC... rsync://address@hidden:PORT]/DEST


cu
Tim