NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/sys/sun/misc/5821

Text File | 1992-12-12 | 1.6 KB | 52 lines

Xref: sparky comp.sys.sun.misc:5821 comp.sys.sun.hardware:6197
Newsgroups: comp.sys.sun.misc,comp.sys.sun.hardware
Path: sparky!uunet!spool.mu.edu!yale.edu!yale!gumby!destroyer!cs.ubc.ca!alberta!cpsc.ucalgary.ca!aycock
From: [e-mail] (John Aycock)
Subject: Re: num-lock LED stays on
In-Reply-To: [e-mail]'s message of Fri, 11 Dec 1992 03:37:38 GMT
Message-ID: <[e-mail]>
Sender: [e-mail] (News Manager)
Organization: UUCP, University of Calgary
References: <[e-mail]> <[e-mail]>
    <[e-mail]>
Date: Sat, 12 Dec 1992 03:58:37 GMT
Lines: 37

This is what I use to fix the locked keyboards with the numlock light on.
It's worked every time for me sofar.  (WARNING: watch out if you're using
it remotely!  Sometimes the user the keyboard locked on isn't logged out
when it becomes unstuck.)  Standard disclaimer applies on the code.  Our
guess is that there's a race condition when the X server exits that causes
this, but we haven't been able to nail it down.  If anyone has had more
luck on this I'd like to hear from you.

BTW, you don't need to be root to run this.
:ja

--
#include <stdio.h>
#include <fcntl.h>

#include <sys/types.h>
#include <sundev/kbio.h>
#include <sundev/kbd.h>

main()
{
    int cmd = 1;
    int fd = open("/dev/kbd", O_RDWR);
    if (fd < 0) {
        perror("open");
        exit(1);
    }
    if (ioctl(fd, KIOCSDIRECT, &cmd) < 0) {
        perror("ioctl(KIOCSDIRECT)");
        exit(1);
    }
    exit(0);
}
--

  //\|_||\|    John D. Aycock        [e-mail]
\/ \/| || |    [phone]        [e-mail]