search for: nohang2

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

...atch This fixes a very common hang problem, and makes -v safe to use again. Since you are also transferring large quantities of files, I would be very interested in knowing if rsync still hangs after applying that patch. If it does, try applying this patch: http://www.clari.net/~wayne/rsync-nohang2.patch The second patch fixes a much rarer bug, and it would be great to know if someone had run into it in simple, real-world conditions. ..wayne.. -------------------------------------------------- How do I apply these patches, could someone help me on that. Thanks in advance Raj ===== ____...

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.

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

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