kit@ATHENA.MIT.EDU (Chris D. Peterson) (01/27/89)
From the xterm manual page:
-C This option indicates that this window should
receive console output. This is not supported on
all systems.
Chris D. Peterson
MIT X Consortium /
Project Athena
Net: kit@athena.mit.edu
Phone: (617) 253 - 1326
USMail: MIT - Room E40-321
77 Massachusetts Ave.
Cambridge, MA 02139 ado@elsie.UUCP (Arthur David Olson) (01/28/89)
> > Is there anyway to get the console output sent to a window rather than > > the background? > From the xterm manual page: > > -C This option indicates that this window should > receive console output. This is not supported on > all systems. Is there a way to do something sensible that can be done with console output *before* xterm kicks in (when xdm's "Welcome" window is on the screen)? -- Arthur David Olson ado@ncifcrf.gov ADO is a trademark of Ampex.
pst@comdesign.UUCP (Paul Traina) (01/29/89)
From article <8901262023.AA03042@DORA.MIT.EDU>, by kit@ATHENA.MIT.EDU (Chris D. Peterson):
x From the xterm manual page:
x
x -C This option indicates that this window should
x receive console output. This is not supported on
x all systems.
This works fine on my Sun when an actual xterm window for the console exists,
but I've noticed that console-message still go to the console when xdm is
just in "login" mode. What we need is a little non-logged-in xterm-like window
that will receive the console messages when xdm is waiting for a user to
login.
Anything like that already in the works?
------
work: pst@condor.cdi.com {apple,pyramid,ucsbcsl,uunet}!comdesign!pst
play: pst@ai.ai.mit.edu {ucsbcsl,comdesign,dscvax2}!nessus!pst
school: pst@cornu.ucsb.edu pst@sbitp.bitnet
"I'm not a scientist, but I play one on TV."kit@ATHENA.MIT.EDU (Chris D. Peterson) (02/07/89)
> Is there a way to do something sensible that can be done with console output > *before* xterm kicks in (when xdm's "Welcome" window is on the screen)? Since there is nowhere to output this information you will have to add something to the system's configuration that will allow you to view console messages. Perhaps an xterm -C that has its translations set to bind all key presses to bell(). This would probabally do the trick but I make no claims as to the security, or lack thereof, of this method. The long and short of it is that you need to provide a method of displaying this information, xdm will allow this to be done via the Xstartup file, but you must provide the program that will actually accomplish the task. Chris D. Peterson MIT X Consortium / Project Athena Net: kit@athena.mit.edu Phone: (617) 253 - 1326 USMail: MIT - Room E40-321 77 Massachusetts Ave. Cambridge, MA 02139
jgarb@CSD360B.ERIM.ORG (Joe Garbarino) (02/07/89)
Concerning an xdm console, Chris Peterson says: >The long and short of it is that you need to provide a method of displaying >this information, xdm will allow this to be done via the Xstartup file, but >you must provide the program that will actually accomplish the task. Maybe I'm missing something, but I don't see how Xstartup solves the problem. According to my reading of the xdm man page: DisplayManager.DISPLAY.startup This specifies a program which is run (as root) after the authentication process succeeds.... To me, this means after a user has typed the username and password, and these are verified as correct. I think the intent is to have a console on the screen continuously, even when no user is logged in. Did I misinterpret the man page? Does it act differently? I hope I'm wrong since I don't feel like digging into xdmshell to hack a solution.... There is a resource named DisplayManager.DISPLAY.reset which could create a console, but I don't think this would work if the server is being restarted for each session (as we do for our Suns). Also, until after the first session, there would be no console. Maybe there should be a DisplayManager.DISPLAY.xdmstartup resource which points to a file which would be executed after the X server is started and before the authentication widget is displayed. This script could create a console, and the DisplayManager.DISPLAY.startup script could remove it. Thanks for looking into the problem. The white trash at the bottom of the screen (console messages), while easily cleared with a C-c, is annoying and hard to explain to novice users. Joe Garbarino ERIM P.O. Box 8618 Ann Arbor, Mi. 48107 (313)994-1200 x2508 jgarb@csd360b.erim.org
bferguso@bonnie.ics.uci.edu (B. Ferguson) (02/08/89)
We have a problem running X11r3 on ULTRIX, where multiple xdm start up. If anyone has a solution to this, or had the same problem, please E-mail to me. Bruce Ferguson.
kit@ATHENA.MIT.EDU (Chris D. Peterson) (02/08/89)
> Concerning an xdm console, Chris Peterson says: > >The long and short of it is that you need to provide a method of displaying > >this information, xdm will allow this to be done via the Xstartup file, but > >you must provide the program that will actually accomplish the task. > Maybe I'm missing something, but I don't see how Xstartup solves the > problem... [discussion of problem deleted] You are absolutely right, this piece of functionality is not provided. Keith and I have talked about this and it looks like the right thing to do here is to add another script that xdm execs. Thanks for the comments, and rest assured that we are looking into the problem. Chris D. Peterson MIT X Consortium / Project Athena Net: kit@athena.mit.edu Phone: (617) 253 - 1326 USMail: MIT - Room E40-321 77 Massachusetts Ave. Cambridge, MA 02139
kit@ATHENA.MIT.EDU (Chris D. Peterson) (02/08/89)
> We have a problem running X11r3 on ULTRIX, where multiple xdm start > up. Xdm starts up one process for each server that it is controlling as well as a process the controls all the server control processes. You should be seeing n+1 processes called xdm on you machine. Where n is the number of displays that xdm is controlling on your machine. If this does not explain your problem let us know and we will try to be of more assistance. Chris D. Peterson MIT X Consortium / Project Athena Net: kit@athena.mit.edu Phone: (617) 253 - 1326 USMail: MIT - Room E40-321 77 Massachusetts Ave. Cambridge, MA 02139
lcn@philtis.UUCP (Leo C. Noordhuizen @ Philips CAD Centre) (02/12/89)
> > > > We have a problem running X11r3 on ULTRIX, where multiple xdm start > > up. > > Xdm starts up one process for each server that it is controlling as well > as a process the controls all the server control processes. You should be > seeing n+1 processes called xdm on you machine. Where n is the number of > displays that xdm is controlling on your machine. > > If this does not explain your problem let us know and we will try to be > of more assistance. I do have the same kind of problems: I am running X11R3 using Ultrix V2.2 on a Vaxstation II GPX. After booting the system, and having started xdm via rc.local, the login is displayed. Peeking in the system via a session logged in via rlogin, ps -ax reveals 3 (three !!) processes running xdm... (Which is one to many if I understand correctly) In addition I am having quite funny ( :-( ) problems: most times when I log out the main process on the GPX (I.e. not all times) the screen is cleared, but nothing happens after this. To be able to use the system again, it is necessary to completely re-initialize the system and re-boot. Any help would be appreciated. (I have been mistrusing the hardware, but Decwindows with VMS runs fine) ---------------------------------------------------------------------------- Leo C. Noordhuizen uucp: mcvax!philmds!philtis!lcn Philips - Corp. CAD Centre phone: 31-40-735834 Building SAQ P343, 5600 MD Eindhoven, The Netherlands