Change how users are quit if they get a write error during the things they do.

Instead of QuitUser inside FlushWriteBuffer() (potentially *UNSAFE*), go back to using SetWriteError(),
but to ensure we dont get a cascade of bad write events from the socket engine, QuitUser the user before
returning in userrec::HandleEvent, after we can gaurantee ALL other reading or writing is done.


git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@5987 e03df62e-2008-0410-955e-edbf42e46eb7

1 files changed, 0 insertions, 1 deletions

diff --git a/src/userprocess.cpp b/src/userprocess.cpp
index 43edb56b1..9aa6d4a31 100644
--- a/src/userprocess.cpp
+++ b/src/userprocess.cpp
@@ -331,7 +331,6 @@ void InspIRCd::DoBackgroundUserStuff(time_t TIME)
 				 * We can flush the write buffer as the last thing we do, because if they
 				 * match any of the above conditions its no use flushing their buffer anyway.
 				 */
-		
 				curr->FlushWriteBuf();
 			}
 		}