Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!husc6!bunny!xg00
From: xg00@GTE.COM (Xev Gittler)
Newsgroups: comp.windows.x
Subject: XKillClient: What does it do, and how to stop it.
Keywords: XKillClient, re-entrant X applications
Message-ID: <7716@bunny.GTE.COM>
Date: 30 Oct 89 19:57:35 GMT
Organization: GTE Laboratories, Inc., Waltham, MA
Lines: 24

I am trying to find out how to stop an XKillClient from actually
killing the client.

A little background:

We are starting to get in X terminals, all run off a central VAX.
Just about everybody is going to want to run an xclock, xbiff, etc,
and it seems sort of ridiculous to have two dozen of these processes
running, particularly when one would do the job adequately. 

So I set out to right a re-entrant X program (using Xt) that would run
in one process and handle multiple displays. The problem I run into is
how X handles a killclient. If one person does a killclient on a
window running from this application, all windows on all displays will
die.  Obviously, this is not a good solution.

So the question is: Is there a way to get X to ignore a killclient, or
at least have the application know that a killclient has been issued,
rather then just killing the windows?

-- 
					Xev Gittler
					xg00@gte.com, or
					xg00%gte.com@relay.cs.net