Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!ncar!tank!uxc!uxc.cso.uiuc.edu!m.cs.uiuc.edu!grunwald
From: grunwald@m.cs.uiuc.edu
Newsgroups: comp.windows.x
Subject: killing clients in xdm
Message-ID: <26900056@m.cs.uiuc.edu>
Date: 13 Dec 88 05:48:00 GMT
Lines: 22
Nf-ID: #N:m.cs.uiuc.edu:26900056:000:921
Nf-From: m.cs.uiuc.edu!grunwald    Dec 12 23:48:00 1988


We're using `xdm' on an ultrix 2.2 based system and have the following
problems that are probably caused by silly configuration problems, but I've
been clueless on how to fix it.

xdm exec's ~/.xsession. If this fails in some way, the clients for that
session might be left running (this occured most recently when xmodmap
barfed because of syntax errors).

At other times, ``rogue xterms'' get unleashed on the system, sucking down
an amazing amount of cpu cycles.

In both cases, the problem seems to be left-over X clients when someone logs
out. This vaxstaion (a color 3200) has a bad-rep in our group because these
xterms are left hanging around by people getting used to X (& debugging their
.twmrc files & xmodmaps).

Is there a way to blast X clients at that point? Would killing the X server
and restarting it be too much? Would that even do what I want?

Dirk Grunwald
Univ. of Illinois
grunwald@m.cs.uiuc.edu