On 23Jun2020 11:57, bruce <badouglas(a)gmail.com> wrote:
Ok...
More testing..
Opened up the dir perms to 775 -- just to see if this was/is an issue.
You'd get a permission error if that were the issue. (There are
scenarios where permissions can produce no-such-file-or-dir, but they
are to do with not being able to read things, not not being able to make
things.)
I just wrote a long message about debugging this, but on reflection I
think your --rsync-path command isn't even starting. I believe, because
the target directory is a local path, that rsync is trying to make it
itself, _before_ running the --rsync-path command for the sync itself.
And that fails because it is doing a plain mkdir(), which does not make
intermediate paths.
To test, run the same command without the --rsync-path and get the same
error message.
_If_ you're really doing this locally, do the mkdir -p outside rsync,
beforehand.
However, I suspect you intend to make this remote soon, otherwise why
bother with --rsync-path at all? So to test that (but using the local
system as a proxy for your final target), make the final target
"localhost:/home/.....". That should cause rysnc to require the
--rsync-path command string as part of the process, so it will run
without trying to make the directory.
Cheers,
Cameron Simpson <cs(a)cskk.id.au>