Re: --compare-dest; I'm missing the boat

Matt McCutchen writes: [...] >> d1a is carbon copy of d1 but still every last file in d1 is copied to >> d2. > > Two paragraphs later in the man page: > > "If DIR is a relative path, it is relative to the destination > directory." > > So you should use: > > rsync -avv --compare-dest="../d1a" d

DO NOT REPLY [Bug 6032] error in rsync protocol data stream

https://bugzilla.samba.org/show_bug.cgi?id=6032 --- Comment #4 from m...@mattmccutchen.net 2009-01-15 18:02 CST --- That is strange, but the output does seem to indicate pretty clearly that rsync is not the thing closing the connection. It's possible that the file is triggering a dat

DO NOT REPLY [Bug 6038] failed: No such file or directory (2)

https://bugzilla.samba.org/show_bug.cgi?id=6038 --- Comment #3 from m...@mattmccutchen.net 2009-01-15 17:55 CST --- The problematic directory is inside the destination, so rsync should have been able to create it. - Do you get any other error messages? - What is the nearest ancestor

Re: --compare-dest; I'm missing the boat

Harry Putnam wrote: I must be seriously misunderstanding the man page coverage of --compre-dest. My take was that if a file in compare-dest=dir matches a file in SOURCE/ then it won't be transferred to DEST/. I tried this test. (d1 has single files and 2 subdir with files) cp -a d1 d1a

Re: --compare-dest; I'm missing the boat

On Thu, 2009-01-15 at 16:54 -0600, Harry Putnam wrote: > I tried this test. (d1 has single files and 2 subdir with files) > >cp -a d1 d1a > >mkdir d2 > > rsync -avv --compare-dest="./d1a" d1/ d2/ > > d1a is carbon copy of d1 but still every last file in d1 is copied to > d2. Two parag

--compare-dest; I'm missing the boat

I must be seriously misunderstanding the man page coverage of --compre-dest. My take was that if a file in compare-dest=dir matches a file in SOURCE/ then it won't be transferred to DEST/. I tried this test. (d1 has single files and 2 subdir with files) cp -a d1 d1a mkdir d2 rsync -avv

DO NOT REPLY [Bug 6041] New: rsync --delete from ext3 to hfs+ always deletes files with special characters in name.

https://bugzilla.samba.org/show_bug.cgi?id=6041 Summary: rsync --delete from ext3 to hfs+ always deletes files with special characters in name. Product: rsync Version: 3.1.0 Platform: x86 OS/Version: Mac OS X Status

DO NOT REPLY [Bug 6038] failed: No such file or directory (2)

https://bugzilla.samba.org/show_bug.cgi?id=6038 --- Comment #2 from jglos...@kennedytech.com 2009-01-15 12:21 CST --- the command im using is rsync -zavPot /critical/svn_trac/trac/ ssh k...@24.56.242.128:/mnt/usb_hd/bigmama_bak -- Configure bugmail: https://bugzilla.samba.org/use

Re: Problem syncing large dataset

On Thu, 2009-01-15 at 17:33 +0100, Maarten Thibaut wrote: > When using rsync-3.0.2 through 3.0.5, I get this error on a large > dataset syncing from machine-a to machine-b: > > $ /bin/rsync -aHSz /local/. machine-b:/local/. > invalid len passed to map_ptr: -1737287498 > rsync error: error in file

DO NOT REPLY [Bug 6038] failed: No such file or directory (2)

https://bugzilla.samba.org/show_bug.cgi?id=6038 m...@mattmccutchen.net changed: What|Removed |Added Summary|failed: No such file or |failed: No such file or

Problem syncing large dataset

Hi, When using rsync-3.0.2 through 3.0.5, I get this error on a large dataset syncing from machine-a to machine-b: $ /bin/rsync -aHSz /local/. machine-b:/local/. invalid len passed to map_ptr: -1737287498 rsync error: error in file IO (code 11) at fileio.c(188) [sender=3.0.5] This happens no

DO NOT REPLY [Bug 6038] New: failed: No such file or directory (2)

https://bugzilla.samba.org/show_bug.cgi?id=6038 Summary: failed: No such file or directory (2) Product: rsync Version: 2.6.6 Platform: Other OS/Version: Windows XP Status: NEW Severity: major Priority: P3 C