Re: [Duplicity-talk] duplicity with scp backend succeeds, but creates no backup

[atharva larisa]

On Fri, Oct 11, 2019, at 12:28 AM, Nate Eldredge wrote:

On Thu, 10 Oct 2019, atharva larisa via Duplicity-talk wrote:

> duplicity -v9 --hidden-encrypt-key address@hidden s scp://192.168.1.98:/tmp/tRD3

This puts the backup in tmp/rRD3 relative to your home directory on 

192.168.1.98.  So you should see a directory called tmp in your home 

directory that contains your backup.

If you want an absolute path, to put the backups in /tmp, add an extra 

slash:

scp://192.168.1.98://tmp/tRD3

Also, the : after the hostname is unnecessary, so you can just write

scp://192.168.1.98//tmp/tRD3

-- 

Nate Eldredge

address@hidden

Thanks a lot Nate. Though is there a reason for such a rebellion against convention ?

Even in the man page, in the initial examples section this extremely surprising behaviour does not seem to be emphasized - e.g.

==================

duplicity /home/me sftp://address@hidden/some_dir

==================

we could have mentioned that this some_dir would be relative to the home of uid in spite of starting with a / ?

thanks again