DO NOT REPLY [Bug 5040] New: multiple mount point directory sources aren't completely recursive

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=5040

           Summary: multiple mount point directory sources aren't completely
                    recursive
           Product: rsync
           Version: 3.0.0
          Platform: x86
        OS/Version: Other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: aaron.pelton at ahs.state.vt.us
         QAContact: rsync-qa at samba.org


OS: SCO 5.0.6a

-----
maybe relevant, maybe not: compiled with iconv enabled but receive an error:
iconv_open cannot open conversion file /usr/lib/nls/conv/_

trying to compile after configure --disable-iconv fails:
Undefined                       first referenced
 symbol                             in file
iconvbufs                           log.o

which is due to ICONV_CONST still being defined
------

actual problem:

/usr/local/bin/rsync  --temp-dir=/usr3/tmp -v --progress --bwlimit=100
--no-blocking-io -a -R --delete --force -x --exclude='/usr3/online_data/**'
--exclude='/usr3/tmp/**' /usr2 /usr3 dbbu:

results in /usr2 having it's subdirectories (/usr2/me, /usr2/you,
/usr2/somebodyelse) but nothing below them. /usr3 appears to be normal.

both /usr2 and /usr3 are mount points but the -x is intended to prevent mount
points below them from being copied and what puzzles me is one works and one
doesn't. Specifying top level non-mount points appears to work normally.

As you would expect, swapping usr2 and usr3 means usr2 works properly and usr3
gets just the top level dirs.

I sincerely hope this is a SCO issue and not worth resolving, but on the off
chance it's otherwise an issue, I'm bothering to make a report. Forgive me if I
missed something in the doc's, I did check!


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.