Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!spool.mu.edu!sdd.hp.com!caen!umich!terminator!pisa.citi.umich.edu!rees
From: rees@pisa.citi.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Installation of X11R4 on apollo
Message-ID: <502114d0.1bc5b@pisa.citi.umich.edu>
Date: 2 Mar 91 20:18:11 GMT
References: <16882@accuvax.nwu.edu> <1991Feb28.051945.20170@agate.berkeley.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Distribution: usa
Organization: University of Michigan ITD
Lines: 16

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.