DO NOT REPLY [Bug 5795] look into a improved tear-down processing during fatal errors

samba-bugs at samba-bugs at
Thu Oct 2 18:53:49 GMT 2008

wayned at changed:

           What    |Removed                     |Added
           Severity|blocker                     |enhancement
             Status|NEW                         |ASSIGNED
            Summary|error in rsync protocol data|look into a improved tear-
                   |stream (code 12) at         |down processing during fatal
                   |io.c(632) [sender=3.0.4]    |errors

------- Comment #2 from wayned at  2008-10-02 13:53 CST -------
Yes, the error reporting coming back from some errors can indeed be lacking. 
However, the pipe-lined nature of the protocol can make this hard to overcome
(the error can be behind so much checksum data that it can't make it back prior
to the connection getting torn down).  In 3.1.0, I have a new option,
--msgs2stderr, that can often be used to debug such situations (for non-daemon

It would be good to investigate a reliable way to drain (and discard) the
pending data to get all the relevant messages more reliably. For instance, if a
new message was added "fatal exit in progress", it could be sent and circle the
3 processes before the connection is torn down.  e.g. a write error on the
receiver sends the error message (text) to the generator, sends the fatal
message too, and then just discards file-change data until it gets the fatal
message back from the sender.

Configure bugmail:
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the rsync mailing list