Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!gatech!hao!oddjob!gargoyle!ihnp4!cbosgd!osu-eddie!bob%tut.cis.ohio-state.edu
From: bob%tut.cis.ohio-state.edu@osu-eddie.UUCP (Bob Sutterfield)
Newsgroups: comp.windows.x
Subject: Re: X periodically dies on Sun 3.2
Message-ID: <3802@osu-eddie.UUCP>
Date: Tue, 14-Jul-87 08:34:53 EDT
Article-I.D.: osu-eddi.3802
Posted: Tue Jul 14 08:34:53 1987
Date-Received: Thu, 16-Jul-87 06:41:39 EDT
References: <1801@megaron.arizona.edu> <3777@osu-eddie.UUCP>
Sender: news@osu-eddie.UUCP
Reply-To: bob@ohio-state.ARPA (Bob Sutterfield)
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 40

In article <3777@osu-eddie.UUCP> bob@ohio-state.ARPA (Bob Sutterfield) writes:
>In article <1801@megaron.arizona.edu> whm@arizona.edu (Bill Mitchell) writes:
>>
>>I recently installed X V10R4 on our 3.2 Suns ...  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:
>>...
>>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.
>
>	Two of our users have complained of the same phenomenon.  They
>think it may be after long periods of typing into a remote client
>without any other activity on the local server - particularly, no
>mouse motion.  It seems that when they jostle the mouse occasionally
>the symptom isn't noticed.

Well, just to call off the bloodhounds who may or may not be looking
for this one (like we were) in the wrong place (like we were):

A couple of local folks have developed extensions to csh to support
EMACS-style command line editing and TENEX-style completion.  Among
the other extensions was a shell variable called `autologout'.  When
autologout is not explicitly unset, or when it is set to some non-zero
value, the shell will kill itself after a period of inactivity.

And sure enough, the console window, closed up and tucked away up in
the corner, often has long periods of inactivity.  And when that shell
kills itself, being the default initial client, it takes the whole
server with it, in a spectacular death rattle of `XIO: socket not
connected' messages.

This may or may not be the problem at other sites, depending upon
whether you have this sort of an extension in your csh.  We suspect
that it was the problem here.
-=-
 Bob Sutterfield, Department of Computer and Information Science
 The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277
 bob@ohio-state.{arpa,csnet} or ...!cbosgd!osu-eddie!bob
 soon: bob@aargh.cis.ohio-state.edu