Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!caip.rutgers.edu!brisco
From: brisco@caip.rutgers.edu (Thomas Paul Brisco)
Newsgroups: comp.windows.x
Subject: Re: fixing Sun keyboard after X failure
Message-ID: <4322@caip.rutgers.edu>
Date: Tue, 4-Aug-87 11:33:20 EDT
Article-I.D.: caip.4322
Posted: Tue Aug  4 11:33:20 1987
Date-Received: Thu, 6-Aug-87 01:39:16 EDT
References: <9997@duke.cs.duke.edu>
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 23
Keywords: X, Sun

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?
> 


	I've found that logging into the sun from the network (or any
other tty) and running "setkeys reset" will fix the problem most of
the time. (The only time I've had problems was in bringing up X11 and
*everything* was in a wierd state).

				Tp.
-- 
                  ----------------------------------------------------------
                  -                  ARPA: Brisco@rutgers                  -
                  -  UUCP: (ihnp4!ut-sally, allegra!packard) !caip!brisco  -
                  ----------------------------------------------------------