Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu!bradley.bradley.edu!pwh
From: pwh@bradley.bradley.edu (Pete Hartman)
Newsgroups: comp.windows.x
Subject: Re: Sun console problem
Message-ID: <1991Feb22.203419.21822@bradley.bradley.edu>
Date: 22 Feb 91 20:34:19 GMT
References: <9102221205.AA01177@lightning.McRCIM.McGill.EDU>
Distribution: usa
Organization: Bradley University
Lines: 27

In <9102221205.AA01177@lightning.McRCIM.McGill.EDU> mouse@lightning.mcrcim.mcgill.EDU writes:
>> I am having a problem with people running X clients off SparcStations
>> onto X-terminals (Sun 3/50s).  The problem is that sometimes the
>> console locks up and it cannot be used to log in or whatever.  From a
>> remote terminal I can start X on the console, or blank it using
>> clear_colormap, but I can't get the getty running on it again.  There
>> IS a getty process, but it won't talk to the physical console.  I
>> think it is something to do with xterm -C which redirects console
>> output to the pty of the xterm, but how can I switch it back again?
>Convince xterm to close the pty.  The easiest way to do this is to kill
>xterm.  (Any xterm -C running on *our* servers gets blown away as soon
>as I notice it.  We don't take kindly to users stealing the consoles
>away.)

Is this a problem with xterms running on the console itself as well?
I've had problems running X on our 4/470 console when it would die in
a non-standard way (i.e. X crash, like running aquarium with a million
things to see how hard we could abuse it), and had to reboot the machine
to get the getty to work again.

I guess what I'm asking is there any other way (besides xterm -C) for
X to hose up the getty on the console?
-- 
-----
Pete Hartman		  Bradley University		pwh@bradley.bradley.edu
    One final word to the young people who listen to this record.  Be cool.
 The retina of the eye quivers to the dance of soundwaves.  Turn on.  Tune in.