https://bugzilla.samba.org/show_bug.cgi?id=3271
------- Comment #2 from [EMAIL PROTECTED] 2005-11-23 22:07 MST ------- I have found that adding "#define SHUTDOWN_ALL_SOCKETS" to config.h (at least on the client side) solves the problem. Without it, the connection is closed with an error (connection reset), rather than with an end-of-file. The server's receiving code handles the error, and it goes into _exit_cleanup and gets all the way to the exit() call, but exit() hangs because it tries to flush a socket that is in an error state. If the client properly closes its sockets, the problem does not occur. Of course, this is only a workaround. It does not handle the case where the connection is legitimately reset because of network errors. It just keeps rsync from foiling itself. A more complete solution in the receiving code is required. -- 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: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
