Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!nrl-cmf!ukma!rutgers!att!ulysses!gamma!sword!arrow!yba
From: yba@arrow.bellcore.com (Mark Levine)
Newsgroups: comp.windows.x
Subject: Re: xterm and R3
Message-ID: <925@sword.bellcore.com>
Date: 1 Nov 88 20:15:25 GMT
References: <178@umigw.MIAMI.EDU>
Sender: news@sword.bellcore.com
Reply-To: yba@arrow.UUCP (Mark Levine)
Organization: Bellcore, Red Bank, NJ
Lines: 20

In article <178@umigw.MIAMI.EDU> angel@umigw (angel li) writes:
>I have build R3 on a Vaxstation 3200, 8 planes GPX color, Ultrix 2.3,
>and have the server running and the clients running.  A major inconvenience
>with this release is that whenever an xterm window goes away, the entire session
>gets logged out.  This gets old quickly.  Has anyone seen this problem?
>
>Another problem seems to be with xdm.  After logging off the main xterm
>window, xdm starts up another X server when another server is already running.
>I ran xdm with "-debug 99" and could not see why this was happening.

[This is a second follow-up from me; I will try and cancel the first]

I have seen this problem also under Ultrix 2.3 on a Vaxstation II/GPX;
when an xterm exits, it seems to propagate a fatal signal all the way back
to the init process.  I run two servers on my vax, Xqdss and Xplx -- an
xterm exiting on either kills both servers!  Other clients do not exhibit
this behavior, so I am going to stare at xterm.  Other opinions, experiences
and especially fixes solicited!

Eleazor bar Shimon, once and future Carolingian
yba@sabre.bellcore.com