Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!srcsip!nic.MR.NET!umn-cs!brsmith
From: brsmith@umn-cs.CS.UMN.EDU (Brian R. Smith)
Newsgroups: comp.windows.x
Subject: Re: Can X die with no fuss?
Message-ID: <14673@umn-cs.CS.UMN.EDU>
Date: 24 Jul 89 16:58:18 GMT
References: <8907240829.AA03112@sunaus.sun.oz>
Organization: University of Minnesota, Minneapolis
Lines: 29

>Path: sunaus!metro!basser!ultima!ckeane

My mailer claims no knowledge of any of those uucp sites...

>Our site runs a net of Suns (mainly 3/50's) and I like to use both
>SunView and X at different times. The Problem is that while SunView
>can be killed with no problem, X doesnt seem to have a shut-down 
>option, and when the relevant processes are killed, it tends to do
>*strange* things to the workstation. Does any know of any graceful
>way of terminating X without re-booting?
>regards...

It sounds like the keyboard state problem that pops up whenever the
server crashes.  It confused me for a while, too.  Check out the
source directory for the Sun server - there is a little program
called "kbd_mode".  You just need to make sure that a "kbd_mode -a"
gets executed after the server exits.  If the server exits gracefully,
it's redundant, but when it crashes...

Make a script that is basically:
#! /bin/sh
xinit
kbd_mode -a

Use that to start X.  Should do it, if that *IS* the problem you're
having.

Brian
brsmith@umn-cs.cs.umn.edu