From owner-freebsd-current Sat Oct 25 19:07:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08922 for current-outgoing; Sat, 25 Oct 1997 19:07:46 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08865 for ; Sat, 25 Oct 1997 19:06:58 -0700 (PDT) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id CAA09303; Sun, 26 Oct 1997 02:04:42 GMT Message-Id: <199710260204.CAA09303@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Alex , current Subject: Re: out of swap space causes hang In-reply-to: Your message of "Sat, 25 Oct 1997 17:59:59 PDT." <19620.877827599@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Oct 1997 02:04:42 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I decided to edit a little xpm today with pixmap. As it was saving the > > pixmap, which apparently is a very memory & time consuming process, my > > computer decided to just completely hang, no panic no nothing. Since this > > 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 :-( > Jordan -- Brian , , Don't _EVER_ lose your sense of humour....