search for: missing_below

The generator can skip a directory's contents altogether due to --ignore-non-existing, a daemon exclude, or a mkdir failure. On a --dry-run, the generator can also note the missingness of a directory while still scanning its contents. These two scenarios were conflated using a single set of missing_below/missing_dir variables in combination with transient increments in dry_run; this caused at least three bugs. Now recv_generator has separate variables for the two scenarios, called skip_dir and dry_missing_dir, respectively. For simplicity, we take the F_DEPTH instead of having separate *_below va...

...edTo: wayned@samba.org ReportedBy: hashproduct+rsync@gmail.com QAContact: rsync-qa@samba.org When rsync fails to create a destination directory, it skips through the file list until it reaches a file whose depth is less than or equal to that of the destination directory (saved in missing_below). This is wrong with --no-implied -dirs because the failed directory could be followed by a deeper file whose parent is not in the file list. I reproduced this as follows: $ mkdir src src/a src/b dest dest/b $ echo data >src/b/file $ chmod u-w dest $ find . -ls 1590269 0 drwx------ 4 matt...

It strikes me that the excluded_below mechanism at the beginning of recv_generator is useless from a security perspective. When a client pushes a daemon-excluded directory, the excluded_below mechanism causes the pushed contents of the directory to be skipped as well as the directory itself. However, the client can just as easily push descendant files individually. If the daemon administrator

I'm trying to rsync files to a set of symlinked directories on an XServe running OS X. The directories look like this: tna@csx:~/2/2006$ l total 80 lrwxr-xr-x 1 tna tna 39 Feb 24 13:18 2006-01 -> /Volumes/CSArchiveArray001/2006/2006-01 lrwxr-xr-x 1 tna tna 39 Feb 24 13:18 2006-02 -> /Volumes/CSArchiveArray001/2006/2006-02 When I run rsync from Linux in --dry-run mode,