From owner-freebsd-current Sun Apr 11 16:18: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B170914C02 for ; Sun, 11 Apr 1999 15:58:50 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA14662 for ; Sun, 11 Apr 1999 13:35:00 -0400 (EDT) Date: Sun, 11 Apr 1999 13:35:00 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.org Subject: swap-related problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that something has broken the good ol' swap behavior. For instance, I have my user-limits set to unlimited and I run something which uses up all RAM. Mallocing never FAILS in the program, as brk() doesn't fail, as etc etc etc. But mallocing continues, all swap space gets used, and both the runaway process and the next biggest gets killed (XF86, of course). Matt, perhaps you can shed light on a. why mallocs still succeed after swap_pager: out of swap space swap_pager_getswapspace: failed is displayed b. why the process continues and gets killed TWICE, or two different processes get killed ? Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message