similar to: rsync --move-files patch

I'd like to revisit the topic of moving files from system to system using rsync. I've just updated my patch from its 2.5.0 version to 2.5.1, and I'm curious what people think about getting it integrated into rsync. The patch comes in two parts. The first eliminates a potential hang condition that can happen if the data channel from the receiver to the generator gets clogged up.

Hello All: I've having repeatable problems copying files between linux machines using rsync-2.5.1 and various recent flavors of openssh. The symptom when testing with a single 2M file is that rsync hangs when when the file is 97% transferred. It seems from looking at various archives that this problem may be non-trivial. I tried applying the patch at

We are running rsync 2.4.6 on HPUX-11and using it to push a document-root from a staging area to several servers running rsync in daemon mode. The rsync client syncs successfully to modules on the same server and to most other machines, but hangs when trying to syncronise across a firewall (from SECURE zone to DMZ) (The firewall port IS OPEN!!) During a normal release where there are rougly

Hi, I have managed to test this same transfer reliably with the Linux boxes and open-ssh, but I am in trouble with the OSF1 4.0 (Digital Unix) being the server sending files from a single directory to the HP/UX 11 - being the client The 'sshd2' (and ssh2) in both ends is installed as root (and starts probably from 'rc') The 'rsync' (2.4.6) in both end is just

I've gone through the CVS commit log and tried to get every user-visible change since 2.4.6, so that we can make a proper announcement for 2.4.7. Please let me know if anything is missing/inaccurate. At this stage I'm planning to release two 2.4.7pre tarballs, one with the "large nohang patch" and one without. Some people inside VA will be stress-testing both, and so we can

Well, here's rsync 2.4.7 preview 1: rsync://va.samba.org/ftp/rsync/preview/rsync-2.4.7pre1.tar.bz2 http://va.samba.org/ftp/rsync/preview/rsync-2.4.7pre1.tar.bz2 You need bunzip2 to decompress these files: http://freshmeat.net/projects/bzip2 The change list is below. Please, do try this out and let us know either if it works for you or if it does not. We need both kinds of

I have a few clients who prepare some reports and put it in their outgoing/ directory for me to pick up every morning. Is there a way to delete those files from their outgoing/ after I fetch them ? Thanks Nishi

If anyone is trying out my --files-from patch, please grab a new version from here: http://www.clari.net/~wayne/rsync-files-from.patch I fixed a potential bug in the pathname-reading code when pulling files. This version also sanitizes all read pathnames, as discussed elsewhere. Remember that this patch is still young, so use it for testing only. ..wayne..

For the small number of people who are checking this out, I released version 0.05 a couple days ago (and only mentioned it on my new-protocol web page) followed today by 0.06. Some highlights of the two releases: - We handle symlinks now in our recursive synchronization mode. - Directory scanning is no longer limited to one active directory at a time (which was sorely needed when all the

There's a program to apply patches, typically called "patch" Try "man patch". If your system doesn't have, and can't get patch, just read the patches and edit the appropriate files by hand. It's not particularly difficult. Incidentally, I want to point out that there's no good reason to cc rsync-admin@lists.samba.org on a regular post. I've been

For anyone who'd like to check out the latest release of my "rzync" [sic] test release, I've just released a new version. For those that might not have time to look at the code but could provide some feedback based on a rough description, I've created the following simple web page: http://www.clari.net/~wayne/new-protocol.html Here's the tar file of the new

Hi, I've been trying to use rsync to backup the content of a large web application on our Digital unix servers. I'm having some success but the main problem is the sheer number of files and subdirectories which must be copied/maintained between the two servers (one is our standby system). Believe it or not there are in excess of 7.5 million files/directories which must be synced between

I found some time in the past week to work on a simple test app that would hopefully help to answer a few questions that came up recently: 1. Can a single-process generator+receiver work well? (Looks good so far, but I haven't run any multi-processor timing tests yet.) 2. How easy is it to use librsync? (Pretty easy.) 3. How small would a transfer-only tool be? (It's currently

I've been having a lot of fun improving my new-protocol testing app. It's seems to be in pretty good shape (for test code), so I figured I'd announce another release for those brave souls that may want to help me in my thinking about a (potential) new rsync protocol. It's a tar.gz file this time because I broke up the code into multiple files. I named it "rzync" just

Rsync release 2.5.6 is now available at http://ftp.samba.org/ftp/rsync/rsync-2.5.6.tar.gz ftp://ftp.samba.org/pub/rsync/rsync-2.5.6.tar.gz rsync://ftp.samba.org/ftp/rsync/rsync-2.5.6.tar.gz There is a '.sig' file at corresponding URLs with a gpg signature; the public key is available on the pgp keyservers. NEWS for rsync version 2.5.6, aka the dwd-between-jobs release Changes

I've worked up a new release of my --files-from patch. It has the following changes from the last release: New Changes: ============ - The -R option is now on by default when --files-from has been specified. The user can specify --no-relative to turn this off. - The -a (--archive) option does not imply -r when --files-from was specified. The user can still specify it manually,

I've released the next version of my rZync test app. You can find a link to it here: http://www.clari.net/~wayne/new-protocol.html You should also snag the referenced librsync source, as some important bugfixes in librsync are needed to compile rzync. For those that don't know, rZync is my new-protocol test app that I'm using to try out some ideas on how to improve the rsync

On Mon, 10 Nov 2003, Wayne Davison <wayned@samba.org>?wrote: > >?... This fix is also in CVS (along with several others). As another poster pointed out recently, it's been a long time since 2.5.6 was released (Jan 28 2003). Many recent replies to questions posted to this list are variants of "It's already fixed in CVS". Are there any particular reasons for holding

Hello, We have used rsync on a mirroring application successfully for just over a year. After our upgrade to 2.4.6, however, the process started failing about 50% of the time. The nature of our failure was that the rsync processes on the remote system would die with no error message, leaving the local system processes hung. I have netstat and trace output for available if needed, but I see

I know this has been discussed repeatedly, so might even say beaten to death, but it is a feature which I need to use. I notice Wayne had a patch to do this listed in the list archives, but I don't know what version of rsync he was patching against. What is the general opinion on using this patch for reliable rsync'ing of extremely small volumes of data of high cost, high latency comms