eap@cs.bu.edu (Eric A. Pearce) (03/17/90)
I think this has been asked before, but I didn't see an answer. A lot of our users have been complaining about logging into the console and having the initial console window not showing up. You can open other windows at this point though. It seems to be random - it does it for different users at different times. Could it be related to system load? I'm not sure what else would vary so much. (This is on a Iris 4D/220 GT running 3.2.1) -e ------------------------------------------------------------------------------- Eric Pearce eap@bu-pub.bu.edu Boston University Information Technology 111 Cummington Street Boston MA 02215 617-353-2780 voice 617-353-6260 fax
root@MCIRPS2.MED.NYU.EDU (03/17/90)
Console window do die in abrupt and unexpected ways on our 70G machine, and many times they do not appear at all . This is bad in that you loose console messages (tape jamed, disk full, etc) that you never get on normal wsh windows. I have noticed it too. Sgi... Are you listenting -- +-----------------------------------------------------------------------------+ | karron@nyu.edu Dan Karron | | . . . . . . . . . . . . . . New York University Medical Center | | 560 First Avenue \ \ Pager <1> (212) 397 9330 | | New York, New York 10016 \**\ <2> 10896 <3> <your-number-here> | | (212) 340 5210 \**\__________________________________________ | +-----------------------------------------------------------------------------+
moss@BRL.MIL ("Gary S. Moss", VLD/VMB) (03/20/90)
I don't know if this is a related problem or not, but executing the postScript
procedure RestartMostThings from /usr/NeWS/lib/NeWS/init.ps, available as a
"restart" selection on my root menu, will cause the console window to go away,
but leave the wsh process running. This unmapped "wsh" causes the console
window to fail to come up, though no error message is evident, on subsequent
attempts to start up a console. Killing the "wsh" process explicitly (i.e.
by exiting the shell or killing the window via the window manager's frame
controls), will fix/avoid this problem. Also, logging out of the console
kills the process.
For your reference, below is the procedure in question:
/RestartMostThings { % kill all windows then start up RestartActions
{ /destroy self send } AllWin
{ /destroy self send } AllChest
StartMostThings
} def
It appears that the console-specific option to wsh ignores whatever signal
is used to kill the processes running in the windows.
Can anyone at SGI shed light on this problem?