samba-bugs at samba.org
2012-Apr-21 14:23 UTC
[Bug 8885] New: Certain directory name results in a strange file being created
https://bugzilla.samba.org/show_bug.cgi?id=8885
Summary: Certain directory name results in a strange file being
created
Product: rsync
Version: 3.0.8
Platform: x64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: sheridan at sheridan.hu
QAContact: rsync-qa at samba.org
Dear All,
The following command results in a file named ".--.Bug6lt" being
created in the
parent directory of "/FTPDATA/-- SYSTEM" (namely, it will be
:"/FTPDATA/.--.Bug6lt")
The file seems to be the original file in every sense except for the name.
Command to reproduce:
/bin/nice ionice -c 2 -n 7 /usr/bin/rsync -va --super --numeric-ids --stats
--progress --no-D --ignore-errors -e "ssh -i /root/.ssh/id_dsa"
/SERVERDATA/FILES/MUNKA/sheridan.tar.bz2.gpg root at
rsync.mysite.hu:/FTPDATA/--\
SYSTEM/
Os: Latest Fedora 16, fully updated with the stable updates, (ie. not the
testing repo).
Regards,
Levente Peres
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
samba-bugs at samba.org
2015-Jul-12 20:05 UTC
[Bug 8885] Certain directory name results in a strange file being created
https://bugzilla.samba.org/show_bug.cgi?id=8885
Wayne Davison <wayned at samba.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Wayne Davison <wayned at samba.org> ---
Your destination path has a space in it, which you must either quote or escape
enough in the local shell that the remote shell gets the right name, or you can
use the --protect-args (-s) option to tell rsync that you want it to preserve
the spaces for you. I can see that would cause rsync to change the destination
path to end at a "--" name, so I'm not sure how the extra dot and
suffix got
there, but I imagine the reason to be related to the above.
--
You are receiving this mail because:
You are the QA Contact for the bug.