Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!aramis.rutgers.edu!mende
From: mende@aramis.rutgers.edu (Bob Mende)
Newsgroups: comp.windows.x
Subject: Re: fixing Sun keyboard after X failure
Message-ID: <1210@aramis.rutgers.edu>
Date: Tue, 4-Aug-87 11:17:50 EDT
Article-I.D.: aramis.1210
Posted: Tue Aug  4 11:17:50 1987
Date-Received: Thu, 6-Aug-87 01:38:25 EDT
References: <9997@duke.cs.duke.edu>
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 31
Keywords: X, Sun
To: ndd@duke.cs.duke.edu


In article <9997@duke.cs.duke.edu> ndd@duke.cs.duke.edu (Ned Danieley) writes:
| We're considering going to X instead of SunView, and I've
| run into a problem: if the X server dies unexpectly, the
| associated keyboard is left in some strange state that renders
| it unusable. This is especially bothersome when it happens on the
| server. I have tried the fixKbd program that was recently posted
| to this group, but it did not appear to have any affect. Does
| anyone know how I can reset the keyboard short of rebooting?

  try invoking X with a command similar to

  xinit uwm ; setkeys reset

  This way the only way that the keyboard will get messed up if the
Machine crashes (then you dont have to worry about the keyboard) or if
the X server dies so badly that the second command dies.  I have only
had this happen to me once and I was issuing the command like this

  exec xinit uwm ; setkeys reset

  This way when I exit x it kills my lowest shell (yes ... a cheap way
to do it ... but it works.).  
  If your keyboard ever gets messed up (and you are on a network or
have an extra terminal connected to your sun) you can type "setkeys
reset" from any terminal on the system.  This is a good feature unless
your under X and someone does it to you.


					Bob
-- 
     mende@rutgers.edu    {...}!rutgers!mende    mende@pisces.bitnet