From owner-freebsd-questions  Sat Aug 23 14:29:04 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA15191
          for questions-outgoing; Sat, 23 Aug 1997 14:29:04 -0700 (PDT)
Received: from x173-171.reshalls.umn.edu (x173-171.reshalls.umn.edu [160.94.173.171])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA15186
          for <questions@freebsd.org>; Sat, 23 Aug 1997 14:28:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by x173-171.reshalls.umn.edu (8.8.5/8.6.9) with SMTP id QAA02348 for <questions@freebsd.org>; Sat, 23 Aug 1997 16:30:01 -0500 (CDT)
Message-Id: <199708232130.QAA02348@x173-171.reshalls.umn.edu>
X-Authentication-Warning: x173-171.reshalls.umn.edu: localhost [127.0.0.1] didn't use HELO protocol
From: mikk0022@maroon.tc.umn.edu
To: questions@freebsd.org
Subject: Low VM killing policy.
Date: Sat, 23 Aug 1997 16:30:00 -0500
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I recently upgraded to XFree 3.3 + Matrox Millenium.  The new server takes
up a lot of memory (RES: 11M according to top).  This causes it to be killed
whenever I get low on VM. 

This is all well and good, except that XFree doesn't give up control of the
console when it dies.  My machine is effectively locked, since I don't have
another machine I can use to contact it.

Is there any way to "protect" a particular process from being killed when the
system runs out of memory?  That is, could I tell the system to sacrifice
Netscape or something?

Alternatively, is there a way that I could arrange to get control of the
console after XFree is killed?

Thanks,
-Chris