[Bug 10951] New: Emtpy parameter triggers unwanted behavior, but no error message

[samba-bugs at samba.org]

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

            Bug ID: 10951
           Summary: Emtpy parameter triggers unwanted behavior, but no
                    error message
           Product: rsync
           Version: 3.1.0
          Hardware: x64
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: stian at wis.no
        QA Contact: rsync-qa at samba.org

If you add a parameter (ex. --exclude <path>) to the rsync command without a
value, you get some unwanted behavior running the command. No error message
will be triggered, and no output will be shown (especially if running the
command from remote server through a SSH session).

We were running the following command for backup of a remote server:
"/usr/bin/ssh -x -l backuppc <servername>.<domain>.lan sudo /usr/bin/rsync
--numeric-ids --perms --owner --group -D --links --hard-links --times
--block-size=2048 --recursive / --exclude --exclude /mnt --exclude
/var/log/tomcat6"

If you check after the "--recursive /" there is two "--exclude" and the first
one without a value. If we run this command there is no output from rsync
before the ssh session outputs a "pipe is broken" message. The rsync continues
to run on the ssh session. There is no output running the command locally
either. 

With the emtpy "--exclude", and a new "--exclude" after the empty one, it seems
like rsync interpits the two exclude folders as destination for syncronization.
We also seem to get at loop when syncing the /mnt folder aswell, due to
syncronization of itself into itself (this is not testet since this happend on
a production server).

When we ran the command written futher up in this text, we got a copy of /
(root) in both "/mnt" and "/var/log/tomcat6". In "/mnt" we also got many
subfolders with their own copies of the root, all folder in root down to the
"/mnt" folder. Seems to be looping.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.