The Samba-Bugzilla – Bug 3334
some time rsync is exiting with received SIGUSR1 or SIGINT (code 20) at rsync.c(229).
Last modified: 2005-12-15 17:12:53 UTC
+++ This bug was initially created as a clone of Bug #2760 +++
Rsync dies consistently after quite some time. My filelist is huge.
Here's the error with 2.6.6 on SLES9 x86_64:
received SIGUSR1 or SIGINT (code 20) at rsync.c(163)
The las guy was using version 2.5.7:
We are running the rsync over the Network, and it is getting killed some
times. The error is as below.
received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
I noticed recently that this message is inaccurate: it also gets output if rsync gets killed by a SIGTERM or SIGHUP. I'd imagine that your OS is killing rsync because it is consuming too much memory (check your system logs to know for sure). I'd suggest dividing the file list up into multiple hierarchies and trying again.