2014-05-20 16:05:40 +02:00
Author: Michal Srb <msrb@suse.com>
Subject: Ignore EPIPE on write.
Patch-Mainline: To be upstreamed
References: bnc#864676
If the VNC server closes connection after our last read and before this write, we will report error message about EPIPE.
This situation is no error, however, we should quit normally same as when we find out that connection was closed during read.
Index: common/rdr/FdOutStream.cxx
===================================================================
2016-09-13 16:12:30 +02:00
--- common/rdr/FdOutStream.cxx.orig
+++ common/rdr/FdOutStream.cxx
2018-08-02 11:24:03 +02:00
@@ -204,8 +204,12 @@ int FdOutStream::writeWithTimeout(const
#endif
2016-09-13 16:12:30 +02:00
} while (n < 0 && (errno == EINTR));
2014-05-20 16:05:40 +02:00
2016-09-13 16:12:30 +02:00
- if (n < 0)
- throw SystemException("write", errno);
2014-05-20 16:05:40 +02:00
+ if (n < 0) {
+ if(errno == EPIPE)
+ n = length; // Ignore EPIPE and fake successfull write, it doesn't matter that we are writing to closed socket, we will find out once we try to read from it.
+ else
+ throw SystemException("write", errno);
+ }
gettimeofday(&lastWrite, NULL);