Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!rutgers!mit-eddie!uw-beaver!rice!sun-spots-request From: viktor@cucumber.princeton.edu (Viktor Dukhovni) Newsgroups: comp.sys.sun Subject: Re: Sun 3 console question Keywords: SunOS Message-ID: <6595@phoenix.Princeton.EDU> Date: 5 Mar 89 22:31:04 GMT References: <8901202003.AA04397@frith.egr.msu.edu> <20329@lll-winken.LLNL.GOV> Sender: usenet@rice.edu Organization: princeton university Lines: 17 Approved: Sun-Spots@rice.edu Original-Date: 23 Feb 89 01:27:55 GMT X-Sun-Spots-Digest: Volume 7, Issue 182, message 1 of 17 X-Issue-Reference: v7n163 casey@lll-crg.llnl.gov (Casey Leedom) writes: >We use standard ascii terminals as the consoles of all our file servers. >After the systems have been up for a while, the terminals lock up and we >haven't figured out how to break them out of that mode. This happens >reliably on two 3/180s and a 3/280 running SUN OS 3.4, and two 3/280s >running SUN OS 3.5 on a whole variety of terminals. Are any of your users using programs like "setkeys" or "caps" (or anything else that uses ioctl() on "/dev/kbd")? Just a keyboard type inquiry is sufficient to hang the ascii terminal on our keyboardless server. I removed "/dev/kbd" and even commented out "device kbd3" from the kernel config file (as well as the dtop, and zs1). The servers kernel is much smaller, and no more hung ascii consoles. Hope this helps. ---Viktor Dukhovni