From 1a59b542f90c10799085ad2b2d8aed2a6c378acf Mon Sep 17 00:00:00 2001 From: brain Date: Thu, 14 Dec 2006 17:58:13 +0000 Subject: 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 --- src/userprocess.cpp | 1 - 1 file changed, 1 deletion(-) (limited to 'src/userprocess.cpp') 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(); } } -- cgit v1.2.3