similar to: List of rsync output / error messages

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 am thinking about a non-standard usage of rsync (at least not mentioned in the man file) I want to synchronized my collegues home directories(trees) each night AND store rsync's internal updating commands (reversed) to be able to restore the state of a directory the day before. This would require - saving the internal updating commands in a separate directory - reversing these commands

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.

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

At the moment, if you start an rsyncd that's not running as root using default settings it will have some trouble. rsyncd tries to use chroot by default, but this will always fail if it's not started by root. It does emit an error message in this case, but I wonder if some people find this a bit confusing until they discover the setting. I have in the past. It might be better that if

Has anybody out there set up a rsync environment that allows mirroring of files between two Windows 2000 servers? Douglas Hornyak Senior Systems Architect Spring Lake Consulting, LLC

Hi Everybody, I'm new to this list, but I have been using rsync for quite some time. First, congratulations to the rsync team for a very fine piece of software! I'm wondering whether rsync could help me to perform the following task: I have 5 million files on one side of the ocean, 100000 of which must be copied to the other side. Both numbers grow with time, and occasionally, some

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 am getting errors when I try and do a dry-run of a local rsync on cygwin on windows 2000. Here is an example command line: /usr/bin/rsync --archive --dry-run --ignore-times --stats --verbose /cygdrive/d/EarthBulletin/data/ /cygdrive/d/EarthBulletin/data_new/ It fails with the following messages: rsync.exe.stackdump rsync: read error: Connection reset by peer rsync error: error in rsync

Help ! I am running rsync as a service on w2k successfully using the patch from http://v.iki.fi/~vherva/cygwin-rsync/ I would like to connect to the windows machine from Linux, to automatically backup the windows machine without user intervention. I understand that there are network problems using the native rsync transport under windows. How do I setup ssh with a w2k server? I have the ssh

Greetings All, I am planning on authoring a web-based (CGI) interface to rsync. The idea is to build a fool-proof interface for my web designers to push content changes from our development server to our live production server. I am talking about an interface which allows point-n-click navigation of file system folders and the ability to push files. These users are both MAC and Windows based. We

Here is the first Perl script I've tried to write to run rsync. It seems to work, but I don't see the progress like I should. I apologize if it's sloppy, I should add that it's not only the first perl script I've written for rsync, it's the first perl script I've written at all. ___________________________ #!/usr/bin/perl -w print " This command will DELETE

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

Hello! As I was found rsync do not detect file renaming. If I just copy my backup.0.tgz (many Mbytes in size having it's md5) to backup.1.tgz (which will be equial in size and md5) it will be the same file in fact... Rsync will delete old file (backup.0.tgz) on the receiving side and download new one (backup.1.tgz). I do not think there are any difficulties to detect this situation and

Chris, to put things in the right prespective, you should read (if you haven't done so already) the original paper describing the design behind batch mode. The design and implementation of this functionality goes back to a project called the Internet2 Distributed Storage Infrastructure (I2-DSI). As part of that project, the authors created a modified version of rsync (called rsync+)

I've just started using rsync, and it's way cool. I checked the FAQ, the broken mailing list archive search function, and scanned the archives, but didn't see this mentioned. I presume it's a fairly common need: I'm mirroring files automatically and daily from one site to another, and anticipate the day when the size of the files may exceed the size of the destination disk.

There is a new patch named "delete-during.diff" in the CVS "patches" dir. This patch adds the ability for rsync to incrementally delete files in each directory during the normal course of the transfer rather than doing a separate delete scan either before or after the transfer. The patch renames the current --delete option into --delete-before and makes --delete behave in the

I have downloaded and built rsync 2.6.0 on our HP ProLiant DL380-G3 servers (2 Hyperthread processors, 4 GB RAM, 840 GB Hard Disk, etc. etc.) running Red Hat 8 with the latest errata kernel (2.4.20-28smp) and updates from HP for RH8. rsync is run in daemon mode from xinetd. When doing transfers the machine requesting the transfer starts to run out of memory. After every rsync transfer there

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

Wayne, I have been using the rsync snapshot from 1/25 for the last few days and everything seems quite solid so far. I include below a few nit-picks in case you're looking for thing to tidy up. I'm also looking forward to hearing news about the --filter option. I'm thinking it is going to be very useful for backup purposes. What I would want to be able to do is, on a