DO NOT REPLY [Bug 5104] New: network copy issues involving filenames ending with a period

samba-bugs at samba-bugs at
Sun Nov 25 06:31:26 GMT 2007

           Summary: network copy issues involving filenames ending with a
           Product: rsync
           Version: 2.6.9
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned at
        ReportedBy: vespira at
         QAContact: rsync-qa at

I have two macintoshes, one running 10.4 and the other running 10.5.  I have
tested both the stock rsync 2.6.3 and the 2.6.9 versions from macports.  The
problem is easily reproduced by trying to sync a directory which has a name
ending in a period.  Performing a local rsync (same machine) results in no
problems.  However when attempting to rsync from either mac to my linux server
(running rsync 2.6.9) the file names get changed.  If, for instance, a
directory is named TEST_1.   and it is rsyncd over the network, the resulting
filename created on the linux server becomes something like TBI9NE~4  

The problem only happens when the file is being created on the linux server
(running gentoo 2007.0).  When the file correctly renamed and sent back to the
macs, all is well.

If the file ending in a period is a file, rather than a directory, it is simply
not copied.  No existence detected on the server.

I have searched the bugs here as well as on google and have not found anything
resembling this issue.  Is this possibly a bug with rsync, or is it simply a
matter of neglecting the proper command line options.  I was syncing with   
rsync -av source user at destinationhost/directory

Configure bugmail:
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the rsync mailing list