Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:3647 comp.os.386bsd.bugs:1458
Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!sdd.hp.com!cs.utexas.edu!uunet!brunix!cs.brown.edu!Mark_Weaver
From: Mark_Weaver@brown.edu
Subject: Re: NetBSD 0.9 + XFree 1.3 -> occasional keyboard hangup
In-Reply-To: Havard.Eidnes@runit.sintef.no's message of Sun, 19 Sep 93 15:50:11 GMT
Message-ID: <MARK_WEAVER.93Sep20183153@excelsior.cis.brown.edu>
Sender: news@cs.brown.edu
Organization: Brown University Department of Computer Science
References: <27f382$7dc@mail.fwi.uva.nl>
<MARK_WEAVER.93Sep18201917@excelsior.cis.brown.edu>
<1993Sep19.155011.9760@ugle.unit.no>
Date: Mon, 20 Sep 1993 22:31:53 GMT
Lines: 22
In article <1993Sep19.155011.9760@ugle.unit.no> Havard.Eidnes@runit.sintef.no writes:
> In article <MARK_WEAVER.93Sep18201917@excelsior.cis.brown.edu> Mark_Weaver@brown.edu writes:
> >Another (hack) way of fixing it is to have /dev/console open by another
> >process so that the driver won't get the close() call. In an xterm you
> >can run "cat >/dev/console", and this should alleviate the problem until
> >XFree86 2.0 comes out.
>
> Or less hacky, perhaps running an xconsole process will do the job...
Sure, that should work too. The way to see if the problem will still
occur is to try resetting syslogd yourself.
You can do this by sending a SIGHUP to syslogd yourself. As root,
type:
kill -HUP `cat /var/run/syslog.pid`
If this makes your console hang, you haven't fixed it.
--
--------------------------------------------------------------------
Email: Mark_Weaver@brown.edu | Box 2160, Brown University
| Providence, RI 02912-2160