From owner-freebsd-hackers Mon Nov 25 21:11:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA09158 for hackers-outgoing; Mon, 25 Nov 1996 21:11:49 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA09146 for ; Mon, 25 Nov 1996 21:11:31 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id QAA01864; Tue, 26 Nov 1996 16:10:54 +1100 (EST) Date: Tue, 26 Nov 1996 16:10:53 +1100 (EST) From: "Daniel O'Callaghan" To: Bruce Evans cc: hackers@FreeBSD.org Subject: Re: Hang your machine with ScrollLock In-Reply-To: <199611260210.NAA20353@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 26 Nov 1996, Bruce Evans wrote: > >> > > As soon as I hit the scroll-lock key, everything was fine- > >> > > all of the uptime processes completed, and name serving > >> > > went on as usual. > >> > >> I belive this to be fixed in what was 2.2-current long ago... > > Nope. There is no bug to fix. Scroll lock says to stop output, so the > tty buffer fills up after a while and the tty driver sleeps on "ttywri". > > Workaround: `comcontrol /dev/console drainwait 10' times out the sleep > after 10 seconds. write() returns -1/EIO or a short count. Applications > may be confused by this. EIO normally means hangup. Would it be possible to put a timeout on the scroll lock, such that after 10 minutes the state is toggled back to 'off'? Danny