rsync - Dec 2005 - [Bug 3334] New: some time rsync is exiting with received SIGUSR1 or SIGINT (code 20) at rsync.c(229).

https://bugzilla.samba.org/show_bug.cgi?id=3334

           Summary: some time rsync is exiting with received SIGUSR1 or
                    SIGINT (code 20) at rsync.c(229).
           Product: rsync
           Version: 2.6.6
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: wek@ppci.com
         QAContact: rsync-qa@samba.org


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


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

https://bugzilla.samba.org/show_bug.cgi?id=3334


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Comment #1 from wayned@samba.org  2005-12-15 17:12 MST -------
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.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.