similar to: Rsync param parsing using --rsh broken? (was: no subject)

Hi, I'm trying to get rsync over OpenSSH/Cygwin working. I started with a command like this (which fails): $ rsync -v -v -v --recursive --rsh="ssh -i /home/ul081b/mpdm-keys/rsa-mpdm01 mpdm@mpdm-w2k3" MPDM-W2K3::MPDM . opening connection using ssh -i /home/ul081b/mpdm-keys/rsa-mpdm01 mpdm@mpdm-w2k3 MPDM-W2K3 rsync --server --daemon . bash: line 1: MPDM-W2K3: command not found

Hi, I'm using rsync/ssh/cygwin to sync two very large directory hierarchies. While testing with one of the subdirectories (this subhierarchy has about 1000 subfolders and 17000 files), I experience the following behavior: rsync 2.6.2 on both ends. Client command: rsync -v -v -r --delete -t --progress --rsh="ssh -l mpdm -i ADMIN/rsa-mpdm01" MPDM-W2K3::"MPDM/17B -

Hi, I'm using rsync/ssh/cygwin to sync two very large directory hierarchies. While testing with one of the subdirectories (this subhierarchy has about 1000 subfolders and 17000 files), I experience the following behavior: rsync 2.6.2 on both ends. Client command: rsync -v -v -r --delete -t --progress --rsh="ssh -l mpdm -i ADMIN/rsa-mpdm01" MPDM-W2K3::"MPDM/17B -

Hi, I'm using rsnapshot 1.3.1 on a Synology Diskstation ds 107+. # uname -a Linux ds107 2.6.15 #832 Sat Mar 7 00:44:45 CST 2009 armv5tejl GNU/Linux rsnpahot uses rsync, on my box there is: # rsync --version rsync version 3.0.6 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit

https://bugzilla.samba.org/show_bug.cgi?id=1582 Summary: rsync dry run cannot find missing folders, contradicts actual run. Product: rsync Version: 2.6.2 Platform: All OS/Version: IRIX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi again all.. When using rsync 3.0 to sync files between 2 local directories, it works as i expect it, but when the destination folder is a mounted smb share, it always copies over the files even though they already exist on the destination. Any ideas on why this is happening? even using the same options, but with a different destination path. I have tried using -vvv, but it doesn't make

Hi, I tried to build rsync-3.0.0pre4 on a list of different plattforms and got some problems with build or test suite. first, the good news: the build and tests worked fine on these plattforms Solaris 5.5.1, 5.6 and 5.8 (sparc) and 5.10 (x86 and sparc) SUSE Linux 9.0 (amd64), 10.1 (amd6) SLES10 (32 and 64 bit) RedHat 7.1 and 9.0 (32 bit) RedHat EL3 (ia64) problems

Everything worked, files transferred fine however a -vvv reveals that the process did not end clean. The error is not seen with -v or even -vv. Any insight? rsync version 2.5.5 protocol version 26, running on Solaris 8. Write failed flushing stdout buffer. write stdout: Broken pipe rsync error: unexplained error (code 255) at main.c(925) _exit_cleanup(code=255, file=main.c, line=925): about to

Kevin Korb via rsync <rsync at lists.samba.org> (So 30 Dez 2018 23:56:44 CET): > I think --partial might be a red herring here. It only applies to what > happens when rsync is aborted in the middle of a file. What happens > without -P? Same happens w/o --partial. I append 2 logs: - a from localhost to remote server, exposing the missing "rename" - b from localhost to

OK, I will do that next. I just tried 2.6.1 on both ends, and it died in a similar fashion. -------Original Message------- > From: Wayne Davison <wayned@samba.org> > Subject: Re: rsync 2.6.2 crash > Sent: 24 Sep 2004 11:21:51 > > On Fri, Sep 24, 2004 at 11:09:26AM -0700, jim wrote: > > The server crashed, but left rsync.exe.stackdump: >

https://bugzilla.samba.org/show_bug.cgi?id=14260 Bug ID: 14260 Summary: leading / added to file name causing file not found when setting permissions Product: rsync Version: 3.1.3 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core

OK, I set up a new PC with a fresh XP load to be my rsync server. Rsync by itself seems to work fine (thank God. I'm going nuts.) I am still having problems when I throw ssh into the mix. At least now, things don't crash, but they do hang. The file list gets build, the transfer starts and it gets through maybe a few hundred files, but then everything stops. All the processes are still

OK. I got the rsync CVS code and compiled under Linux. That did the job, but only with --no-whole-file because of the local transfer. I then tried to read-batch... under Windows / Cygwin with the current Cygwin rsync. That didn't work - as expected. After compiling again under cygwin it worked! I can now create a diff from a new CD to the version before and send the diff files by email. On

I think --partial might be a red herring here. It only applies to what happens when rsync is aborted in the middle of a file. What happens without -P? Also, it is worth trying with --inplace. On 12/30/18 5:32 PM, Heiko Schlittermann via rsync wrote: > Hi, > > I used --partial to transfer files from my local computer (rsync 3.1.2, > Debian) to a remote computer (rsync 3.1.1 WD

Hello, I have 2 servers I'm synchronizing using rsync, I have a situation where I : 1. rsync from rnd-dev2 to rnd-dev1 2. change the rsynched file on rnd-dev1 3. rsync from rnd-dev2 to rnd-dev1 again 4. File gets overridden on rnd-dev1 over though it has newer change time then file on rnd-dev2. here is the bug(?) reproduction: [root@rnd-dev1 test_rsync]# rsync --version rsync version

I am puzzled as to why I can't get the option --link-dest to work properly. When I use this option when both source and destinations are on a local filesystem the hard-linking of the target against the link-dest directory does work, but when the source is a remote directory (via ssh or rsync server) hard links are not created. I suspect it has something to do with setting the correct

I'm having a problem with large files being rsync'd twice because of the checksum failing. The rsync appears to complete on the first pass, but then is done a second time (with second try successful). When some debug code was added to receiver.c, I saw that the checksum for the remote file & the temp file do not match on the first try, so (as expected) it repeats the rsync & the

Hi, I used --partial to transfer files from my local computer (rsync 3.1.2, Debian) to a remote computer (rsync 3.1.1 WD MyPassport Storage device) The files get transferred, but after successful transfer, the files are not renamed from .<tmpfile> to <file>. Where to go next? Here is the verbose output after transferring an empty file heiko at blade:~/Pictures$ rsync

I have two large files (2+MB), one of which is a corrupted version of the other. I tried to rsync the good file to the corrupted one, hoping it would repair the few bad bytes, but it did nothing. (I tried to be careful not to specify the --archive or --update flags, either explicitly or implicitly.) The original problem occurrend on a transfer from one computer to another. I then did a number

I can't say I have any idea why rsync would just skip that step and I can't duplicate it myself. Your only recourse might be to use --inplace on that system. On 12/31/18 12:33 PM, Heiko Schlittermann via rsync wrote: > Kevin Korb via rsync <rsync at lists.samba.org> (So 30 Dez 2018 23:56:44 CET): >> I think --partial might be a red herring here. It only applies to what