[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] rsync to rsync.net
From: |
rsync.net |
Subject: |
Re: [Duplicity-talk] rsync to rsync.net |
Date: |
Tue, 18 Apr 2017 16:12:46 -0700 (PDT) |
User-agent: |
Alpine 2.00 (BSF 1167 2008-08-23) |
Ken, et. al,
On Tue, 18 Apr 2017, Kenneth Loafman via Duplicity-talk wrote:
I think I see it... Is there really a colon at the end of the duplicity
command? That could throw the URL parser off.
rsync.net uses a "default" directory with *NO* leading forward slash ...
so if you were doing a plain old rsync, the command would look like:
rsync -avH /your/files address@hidden:
or, if you had a destination directory here:
rsync -avH /your/files address@hidden:some/dest/folder
... the bottom line is, there is no *leading* slash in the remote
address@hidden:path ...
I do not know the proper duplicity translation of this to get the command
line this user (our customer) wants, but I hope this clarifies it for you
...
Thanks,
John Kozubik
rsync.net, Inc.
- [Duplicity-talk] rsync to rsync.net, Manuel Morales, 2017/04/18
- Re: [Duplicity-talk] rsync to rsync.net, edgar . soldin, 2017/04/18
- Re: [Duplicity-talk] rsync to rsync.net, Manuel Morales, 2017/04/18
- Re: [Duplicity-talk] rsync to rsync.net, Kenneth Loafman, 2017/04/18
- Re: [Duplicity-talk] rsync to rsync.net, Kenneth Loafman, 2017/04/18
- Re: [Duplicity-talk] rsync to rsync.net,
rsync.net <=
- Re: [Duplicity-talk] rsync to rsync.net, Kenneth Loafman, 2017/04/18
- Re: [Duplicity-talk] rsync to rsync.net, Manuel Morales, 2017/04/22
- Re: [Duplicity-talk] rsync to rsync.net, Manuel Morales, 2017/04/22