From owner-freebsd-bugs Mon Feb 2 18:15:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02984 for freebsd-bugs-outgoing; Mon, 2 Feb 1998 18:15:11 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02975; Mon, 2 Feb 1998 18:15:09 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id SAA14583; Mon, 2 Feb 1998 18:10:13 -0800 (PST) To: Donn Miller cc: current@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: netscape/swap_pager causing problems with syscons In-reply-to: Your message of "Mon, 02 Feb 1998 13:38:53 GMT." Date: Mon, 02 Feb 1998 18:10:13 -0800 Message-ID: <14579.886471813@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-bugs" > This problem was alluded to before. When running X windows, say you start > netscape. Then you run out of swap space. What happens next is that X > windows lock the computer solid, or X windows crashes, leaving me with a > blank screen. None of the virtual terminals work then, but I know the > system is still running, because ctrl+alt+delete reboots (shuts down) the > system. But I still see nothing on the screen. > > Jordan hinted to this as a problem with syscons in one posting I saw. I Nope, it's not a "problem" with syscons - it's just what happens when an X server is rudely shot down and has no chance to clean up. And I'm sure that Terry will have some suggestion about how state changes should be pushed and restored in syscons but it's unlikely that this will every happen unless somebody actually figures out how to implement it and has the free time to do the work involved. Don't hold your breath though and allocate more swap space instead. ;-) Jordan