From: Martin Pool Date: Tue, 12 Mar 2002 06:08:36 +0000 (+0000) Subject: If we get an error writing to a socket, then we should perhaps X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/commitdiff_plain/89b0a3d963097d8b1f7d807d8bd617c1477937b4 If we get an error writing to a socket, then we should perhaps continue trying to read to see if an error message comes across explaining why the socket is closed. I'm not sure if this would work, but it would certainly make our messages more helpful. --- diff --git a/TODO b/TODO index 2fb7642e..e2d1cc19 100644 --- a/TODO +++ b/TODO @@ -205,6 +205,11 @@ Errors eof" give a message that is more detailed if possible and also more helpful. + If we get an error writing to a socket, then we should perhaps + continue trying to read to see if an error message comes across + explaining why the socket is closed. I'm not sure if this would + work, but it would certainly make our messages more helpful. + File attributes Device major/minor numbers should be at least 32 bits each. See