similar to: Rsync'ing lists of files

Rsync list: Alberto and I have done a couple more exchanges by private email, and we found that he wasn't turning on my include/exclude optimization in his test because he had an "exclude" directive in rsyncd.conf. He has now removed that and run the test again. His very interesting results are below with my comments. Note that his case is rather pathological because he's got

I'm rsync'ing an rdiff-backup repository to a different machine and I have a few questions I'm hoping you guys can help me out with. Should I use --archive? Or maybe -rlD instead? Can I restrict an SSH key to rsync? I can do it with rdiff-backup with command="rdiff-backup --server" but I can't figure out how to do it with rsync. The rdiff-backup repository I'm

I'm using rsync to copy some large (>1GB) oracle datafiles. I've noticed that sometimes it transfers some of the files twice. Some earlier posts to this list that I saw in the archives seemed to indicate that this is a problem with the rsync algorithm itself when dealing with large files. Some of the mails seemed to indicate that this can be mitigated by using larger block sizes,

I am running latest rsync version 2.6.8 on both ends. The receiver is a daemon. When I transfer a symbolic link like this: /tmp/rsync -av /opt/iat/IaT3.1.1/bin/* uxgary::root/opt/iat/IaT3.1/bin building file list ... done compile_plan.py -> ../python/compile_plan.py iat_status -> ../python/iat_status.py load_iat_xml.py -> ../python/load_iat_xml.py show_engine.py ->

I know this has come up a bit in the past, but consider this situation: Two Samba4 DC's - and I want to "mirror" the data shares to the "backup" DC in case we lose the primary DC and it's file shares. [A cheap, dirty, poor-mans semi-CTDB. How did you ever guess that Red Green was helping me?!] The easiest way is probably rsync'ing the data. However, will that

Hi all. This looks like a common question. I want to backup a dir, in which i put some symlinks, so it looks like machinegun:/tmp/daily_backup # ls -la total 8 drwxr-xr-x 2 root root 4096 2010-02-17 17:41 . drwxrwxrwt 19 root root 4096 2010-02-17 17:30 .. lrwxrwxrwx 1 root root 16 2010-02-17 17:41 cgi-bin -> /srv/www/cgi-bin lrwxrwxrwx 1 root root 4 2010-02-17 17:17 etc -> /etc

Dear all, I've been trying to track down a problem with timeouts when pulling data from an rsync daemon and I have now run out of any useful ideas. The problem manifests itself when I try to transfer a large directory tree on a slow client machine. What happens then is that the client rsync process successfully receives the list of files from the server, then begins checking the local

When rsync'ing to a module with rsync -a I have a file appear with the proper owner, but not the proper group set. Below is the module, is it functionally possible to hard set the group like the user while still using the -a flag with rsync. max connections = 25 timeout = 600 secrets file = /etc/rsyncd.secrets lock file = /var/tmp/rsyncd.lock list = yes [release] comment = Release

--exclude-from and --cvs-exclude currently do not accept exclude files that use CR/LF (DOS-style) line breaks. It basically behaves as if the files are empty. This is rather annoying if the exclude files are generated by Windows systems (e.g. if you're using --cvs-exclude and rsync'ing the contents of a Samba share that includes .cvsignore files). Attached is a simple 1-line patch (for

I, too, was disappointed with rsync's performance when no changes were required (23 minutes to verify that a system of about 3200 files was identical). I wrote a little client/server python app which does the verification, and then hands rsync the list of files to update. This reduced the optimal case compare time to under 30 seconds. Here's what it does, and forgive me if these sound

I was at first, but then removed it. The results were still insufficiently fast. > Were you using the -c option of rsync? It sounds like you > were and it's > extremely slow. I knew somebody who once went to > extraordinary lengths to > avoid the overhead of -c, making a big patch to rsync to > cache checksums, > when all he had to do was not use -c.

I just took a look at the 2.5.5 codebase to see how easy it would be to write a little driver script that downloads a big directory tree from an rsync daemon the chunky way (get a list of a module's subdirectories and do the transfer by subdirectory). The reason for doing this is obvious when you have large directory trees, as is the case for many of us. Unfortunately the way list_only is

Hi, I have compiled the new version 2.5.2 rsync in our servers, then ran rsync last night, there were some files not copied to destination server, both source and destination servers are running 2.5.2, I got the following error messages, can you please let me know what would be caused the errors? I copied back 2.3.2 version on both servers, and rsync went well. Thanks for the help, here is

Is there any chance this can be added into the distribution as it sounds really nifty. Another suggestion unless I have read the following - would it be useful to have a command option in rsync to generate the file list by doing the "find" and outputting into a standard format? (As this would make it less OS specific or kludgy?) Cheers, Lachlan. At 16:06 19/11/01 -0500, you wrote:

I am trying to finalize the use of rsync for updatiung a new nfs server before we take the old one offline. I keep getting the following warning during the rsync process: Warning: unexpected rad size of 0 in map_ptr Any ideas where this comes from and how to make it go away? I am using rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7. Bob roconnor@vectorpartners.com

The second rsync-2.5.6 pre-release version is now available at: http://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre2.tar.gz ftp://rsync.samba.org/pub/rsync/preview/rsync-2.5.6pre2.tar.gz rsync://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre2.tar.gz There's also a corresponding '.sig' file that contains a gpg signature of the file; the public key is available on the

Howdy, We occassionally get the following error when running our nightly backups: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) This happens more on one or two machines than on any of the others. We've looked high and low to see if we're mistakenly sending these signals, but nothing is that we can find. Does anyone know what this might be from? Is it the server

How long does one have to typically wait for an answer to a post? Tomorrow my message will have been up a week, and I've gotten no replies. It was about whether a file, while it was being written to, could subsequently be opened by another client for reading. I used a DVR with chasing play as an example. Didn't seem like that difficult of a question, but maybe it isn't geeky

I get the following log messages using rsync 2.5.1 compiled on Solaris 8 when using the "hosts allow" option in rsyncd.conf: 2002/01/23 12:09:51 [28276] rsync: reverse name lookup mismatch on fd0 - spoofed address? 2002/01/23 12:10:18 [28276] rsync: connection unexpectedly closed (16 bytes read so far) Resolv.conf/DNS are configured and working properly with both A and PTR records

I just noticed (at least on OpenSSH 3.0p1) that even though I have both RSA and DSA keys available in sshd_config on a server, only a ssh-rsa line shows up in known_hosts on the client side, not a ssh-dss line (that priority may come from the fact that my RSA key is listed before my DSA key in sshd_config). If I comment out the RSA key in sshd_config and restart the server, then the next time the