exit status 13 in version 3.1

Wayne Davison wayned at samba.org
Sat Nov 7 10:38:04 MST 2009

On Wed, Nov 4, 2009 at 8:05 PM, Matt McCutchen <matt at mattmccutchen.net>wrote:

> With commit 84c11e85a4c4a12ecacba24afe9617222e4361e6, I get different
> output, but still not the desired "No space left on device":

Yeah, that's the long-standing issue where a fatal error on the server side
can cause the client side to get a socket error trying to write to the
socket before it has a chance to read the error(s) from the socket.  The
latest git archive finally has a fix for this.  It should make the exit
messages much cleaner for an abnormally-exiting protocol 31 transfer, both
receiving the final error from the server and exiting with the proper error
code.  When an older client is talking to a new server, the error should
also make it to the client, but the client will exit with the (sadly)
traditional error about an unexpectedly closed connection.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/rsync/attachments/20091107/893fdb1d/attachment.html>

More information about the rsync mailing list