no such file or directory - but hey, the files are there!

Matt McCutchen hashproduct+rsync at
Wed Dec 27 16:08:49 GMT 2006

On 12/26/06, Tomasz Chmielewski <mangoo at> wrote:
> Wrong - in "/uDrive/backup" example, "uDrive" is a root, and "backup" is
> a subdir.
> [...]
> In the second example, the root is still "uDrive", but we want to
> transfer everything that's under "backup/fileacl" (or whatever deeper
> under "backup").
> Or maybe that's what you meant.

By "the root of the transfer" I mean the directory that corresponds to
"./" in the file list, because this is the directory into which the
sender pushes to scan files into the file list (see flist.c).  When
--relative is off, this is the directory ending at the last slash in
the source argument.  Since you did not use a trailing slash, the root
of the transfer is /uDrive/ in the first example and /uDrive/backup/
in the second example.

> Funny is, for some other module names, sometimes, I can access a second
> directory (like, "/sDrive/first/second" copies fine, where
> "/uDrive/backup/fileacle" does not).
> But I didn't discover a pattern (when it works, when it doesn't work) yet...

Maybe the working modules had paths that didn't start with a
Windows-style drive letter?

Anyway, the important thing is that your setup works now.


More information about the rsync mailing list