Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!agate!whirlwind.Berkeley.EDU!mehlhaff
From: mehlhaff@whirlwind.Berkeley.EDU (Eric Mehlhaff)
Newsgroups: comp.sys.apollo
Subject: Re: Installation of X11R4 on apollo
Message-ID: <1991Mar3.061142.23920@agate.berkeley.edu>
Date: 3 Mar 91 06:11:42 GMT
References: <16882@accuvax.nwu.edu> <1991Feb28.051945.20170@agate.berkeley.edu> <502114d0.1bc5b@pisa.citi.umich.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Distribution: usa
Organization: UC Berkeley Open Computing Facility
Lines: 41

In article <502114d0.1bc5b@pisa.citi.umich.edu> rees@citi.umich.edu (Jim Rees) writes:
>In article <1991Feb28.051945.20170@agate.berkeley.edu>, mehlhaff@hailstorm.Berkeley.EDU (Eric Mehlhaff) writes:
>>
>> 	I've had similar problems here.  And some new ones.  Basically, the
>> clients not communicating with the server seems to be a random thing, and 
>>  doesn't happen all the time.  Maybe 1 in 20 can't connect.  But if that one is
>> the one at the end of your Xsession, well, then you get logged out...
>
>I don't know if this is your problem, but...
>
>You shouldn't try to use UDS for X.  UDS has bugs related to the size of
>messages you pass through it.  Besides which, it's actually slower than TCP.
>
>Turn on your loopback interface ("lo0") and use that instead.  Either put
>"localhost" in /etc/hosts or set your display to the dotted-decimal address
>so you don't have to go through name service every time you start up an X
>client.
	I have been setting the dotted-decimal addresss!  Here's a sample from a random
xdm-errors file:
XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
      after 45 requests (37 known processed) with 0 events remaining.
      The connection was probably broken by a server shutdown or KillClient.
XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
      after 6782 requests (6780 known processed) with 3 events remaining.
      The connection was probably broken by a server shutdown or KillClient.

Other than these errors, I'm getting a lot of Invalid Argument errors, but I I think that's
something different:
XIO:  fatal IO error 22 (Invalid argument) on X server ":0.0"
      after 201 requests (194 known processed) with 0 events remaining.


Here's another bug that's made itself really annoying:
	Periodically, xclocks and oclocks will seem to take over the machine.  Unsuspecting
users who are running these programs find their machines locking up every once in a while, 
and the only way of freeing the machine is rsh-ing in and killing the clock.   I saw mention
of a clock bug on apollos here not too long ago. Is this related?

-------------------------------------------------------------------------------------------
ERic  Mehlhaff					printer-czar@ocf, mehlhaff@ocf.Berkeley.EDU
The OCF -- BAD computers for BAAD people