Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!oddjob!hao!noao!arizona!whm
From: whm@arizona.edu (Bill Mitchell)
Newsgroups: comp.windows.x
Subject: X periodically dies on Sun 3.2
Message-ID: <1801@megaron.arizona.edu>
Date: Tue, 7-Jul-87 19:45:37 EDT
Article-I.D.: megaron.1801
Posted: Tue Jul  7 19:45:37 1987
Date-Received: Sat, 11-Jul-87 01:19:01 EDT
Organization: U of Arizona CS Dept, Tucson
Lines: 29

I recently installed X V10R4 on our 3.2 Suns and 4.3+NFS VAXs and it seems
to work just fine for the most part.  However, during my usual mode of use,
running xinit on my Sun and rsh somevax xterm mysun:0, I get dropped back
out to where I started xinit from csh.  That is:


<login on Sun, get csh prompt #1>
xinit
<X starts up and I use it for a while>
<poof -- I'm looking at csh prompt #2>


There seems to be no pattern to when this happens.  Sometimes it'll last all
night, sometimes less an hour or so.  It's gotten me both after long periods
of inactivity and between keystrokes.

I've tried checking $status after xinit exits, but it's 0 and there's no
core dump that I can find.  Often, when I try to start another xinit after
getting dumped out, xinit will say "No such display server unix:0".  I found
that if just persist, xinit eventually works.

I like X a lot, but it's really irritating to have a bunch of windows up,
some su's going, an Emacs or two, and then have all that blotted out.

Any ideas or suggestions will be greatly appreciated.

					Bill Mitchell
					whm@arizona.edu
					{allegra,ihnp4,noao}!arizona!whm