Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bionet!ames!elan!jlo
From: jlo@elan.elan.com (Jeff Lo)
Newsgroups: comp.windows.x
Subject: XIO errors again
Keywords: XIO errors KillClient writev error codes
Message-ID: <579@elan.elan.com>
Date: 19 Jul 89 23:56:05 GMT
Reply-To: jlo@elan.com (Jeff Lo)
Organization: Elan Computer Group, Inc., Mountain View, CA
Lines: 15

This subject has appeared before, but I never heard any real definitive
answers or solutions to the problem.  The problem is that sometimes an
X client seems to fall behind the server, or a very large amount of data
is being sent between the client and the server, and the server appears
to send a KillClient, and consequently the client dies.  I have heard
some say that there is a bug in writev and it returns an incorrect
error code.  Others have said that it is caused by buggy unix domain
sockets (we've gotten the error when client and server were on the same
machine and when they were not).  In any case, it is causing us a lot
of grief, so I was wondering if anyone has found a fix, a good explanation,
or even a "Fixed in R4" comment.  Thanks!
-- 
Jeff Lo, Elan Computer Group, Inc.
jlo@elan.com, ..!{ames,uunet}!elan!jlo
888 Villa Street, Third Floor, Mountain View, CA 94041, 415-964-2200