<div class="gmail_quote">On Wed, Nov 4, 2009 at 8:05 PM, Matt McCutchen <span dir="ltr"><<a href="mailto:matt@mattmccutchen.net">matt@mattmccutchen.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div>With commit 84c11e85a4c4a12ecacba24afe9617222e4361e6, I get different<br></div>
output, but still not the desired "No space left on device":<br>
<div class="im"></div></blockquote><div><br>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.<br>
</div></div><br>..wayne..<br>