Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!lib!pauling!klong
From: klong@pauling.bcm.tmc.edu (Kevin Long)
Newsgroups: comp.windows.x
Subject: xterm -C takes over hosts/X consoles
Keywords: xterm console NCD X Solbourne Sun xtools
Message-ID: <229@lib.tmc.edu>
Date: 22 Aug 89 16:16:51 GMT
Sender: usenet@lib.tmc.edu
Lines: 36


I try to keep up with comp.windows.x, so forgive me if this question
has been posted recently.

I've got a bunch of NCDs configured to give users, among other
things, an xterm window that I want to act more or less as a console.
Problem is, when I give xterm the "-C" option, it takes over the real console
from the host on which it's running, and the user starts seeing all kinds
of system messages intended for the operator.  The "host" here is
a solbourne, but the same thing happens on our sun-3s running SunOS 4.0.3.

I'd like to make a designated xterm the "console" only for the msgs the user
*should* see (complaints from programs, xwatch and xwininfo entries, etc.).
What I'm hoping to avoid is running all of my programs from this
"console" xterm; instead, I'd like to have  xtools (perhaps called from
the .login or from xdm) handle everything.

I'm willing to run everything from the same host on which this xterm is 
running, but I'm beginning to wonder whether this problem isn't deeper.

Is there some sort of 
    "I've registered myself with the X server on this display as the 
     <<console window>>, so all programs on all hosts running on this 
     display can send your messages to me!" 
ability present in or planned for X that all programs could use?

Is there a way to accomplish what I'm trying to do?

Thanks,

	Kevin Long
	Baylor College of Medicine
	One Baylor Plaza
	Houston, TX 77030
	(713) 798-6116
	klong@bcm.tmc.edu