https://bugzilla.samba.org/show_bug.cgi?id=1442
Summary: rsync sender appears to hang when receiver recounters an error Product: rsync Version: 2.6.2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] As sent to the rsync mailing list on May 4, 2004: (rsync 2.6.2 between two Linux systems) ... What happens is that the sending rsync just appears to hang. The receiving rsync processes are no longer running when I go to look, typically the next morning. I finally managed to capture an strace of the receiving rsync processes, which I've attached below. The child receiver process gets an error return on a write(), informs its parent by sending it two error messages, and calls exit(11). The parent receiver process reads the first of the two error messages, but not the second. It handles the SIGCHLD signal after read()ing the first error message. Thereafter, the patent's select() no longer includes the file descriptor on which (presumably) the second error message is waiting. And it never informs the sending rsync process of the error. (strace output) ... -- 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: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html