similar to: rsync w/ openssh hangs on linux

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.

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

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

Martin, I want to remind you that there's still an open issue regarding copies when both source and destination are on the local machine (including over NFS): I put a patch into the CVS to automatically imply the '-W' option in that case, and somebody said he was concerned about that because he found that with -W on local copies he had cases where rsync would lock up, and it

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

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

That's the way it is. If it's really a one-off change, a huge change in your structure, telnet ssh, rsh, and so forth, work really well for dropping in and deleting stuff (unless you're supplying the master, and other systems out of your control copy from you). Rsync is optimized for taking a filesystem in an unknown state, and making it identical to another filesystem in an unknown

Hi! I've been looking for a solution to periodically pull files from a server and delete them after a successful download. rsync + the --move-files patch seems to be the perfect solution for it as I can run it through ssh. I've found the following download location in the mail archive: http://www.clari.net/~wayne/rsync-nohang.patch http://www.clari.net/~wayne/rsync-move-files.patch

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

Hello Everyone: I've been trying to get rsync using --bwlimit using openssh for transport without success. Here's what I get: % rsync --bwlimit=20 from.com:/dir/file.txt /dest user@from.com's password: **** rsync: unrecognized option `--bwlimit=20' unexpected EOF in read_timeout I tried specifying ssh transport using both the -e option and by setting the RSYNC_RSH

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 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

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

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

Hi all, rsync-2.4.6 has been running for quite a while with no problems, until about a week ago when for some reason it blocked on the same host ever time. I use it to backup about thirty hosts to my backup server, but for some reason it's illiciting that blocking bug that some people experience with 2.4.6. So, I upgraded the client side with 2.4.7, but it complained of protocol differences.

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

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

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..

Hi, I got stuck within some weird prob concerning my 2-node linux cluster and the synchronisation tool at hand (rsync-2.5.1pre1). I have to copy a structure of 70 directories where the data of these directories are hardlinked to the data of the 1st directory. Within this "orig data" directory, I have about 30.000 files, so the amount of files to sync is approx. 2.100.000. The

I just ran this again and got this error: leelab/NCBI_Data_old/GenBank/htg write failed on leelab/NCBI_Data_old/GenBank/htg : Error 0 rsync error: error in file IO (code 11) at receiver.c(243) Received signal 16. (no core) rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) The command I am running is: /usr/local/bin/rsync -auv --delete --rsh=/usr/bin/ssh lpgfs104:/share/group/*