From owner-freebsd-current Sat Oct 25 19:23:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09956 for current-outgoing; Sat, 25 Oct 1997 19:23:09 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (garbanzo@korea-130.ppp.hooked.net [206.169.225.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA09939 for ; Sat, 25 Oct 1997 19:23:01 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id TAA03282; Sat, 25 Oct 1997 19:22:16 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 25 Oct 1997 19:22:13 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Brian Somers cc: current Subject: Re: out of swap space causes hang In-Reply-To: <199710260204.CAA09303@awfulhak.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 26 Oct 1997, Brian Somers wrote: > > Are you sure it hung or did the X server just get shot down for eating > > too much memory? Since getting shot down leaves your screen and > > keyboard in a seriously hosed state, unless you can actually telnet > > in or ping the box externally, it looks just like a crash. > > This is annoying if you do actually crash. Is there any reason why > ddb can't reset the screen & keyboard ? I suspect (although I know > next to nothing abouth this) that putting the screen & keyboard into > a know state is an ``art'' that depends on knowing what specific > hardware is there :-( DDB won't work if they keyboard's not responding, unless it works telepathically now. ;-) - alex